Commit 2bed40c
authored
Bump jupyterhub/repo2docker-action from b3cd89ff99f95b00abb5b4db27ec49bb4d3f8c85 to 00874a0abfebce00bab7eaa3332d3da603c5a2c2 (#440)
Bumps
[jupyterhub/repo2docker-action](https://github.com/jupyterhub/repo2docker-action)
from b3cd89ff99f95b00abb5b4db27ec49bb4d3f8c85 to
00874a0abfebce00bab7eaa3332d3da603c5a2c2.
<details>
<summary>Changelog</summary>
<p><em>Sourced from <a
href="https://github.com/jupyterhub/repo2docker-action/blob/master/RELEASE.md">jupyterhub/repo2docker-action's
changelog</a>.</em></p>
<blockquote>
<h1>Making a release</h1>
<p>Releases are automated through
<a
href="https://github.com/jupyterhub/repo2docker-action/blob/HEAD/.github/workflows/release-updates.yaml">.github/workflows/release-updates.yaml</a>.</p>
<p>To cut a release, visit the projects <a
href="https://github.com/jupyterhub/repo2docker-action/releases">releases
page</a> where
you create a new GitHub release. Enter a <em>tag name</em> and
<em>release name</em> of
"vX.Y.Z". Doing so will automatically update the
"vX" branch allowing users to
reference this action with
<code>jupyterhub/repo2docker-action@vX</code>.</p>
<p>If you are to cut a major release, make sure to also update
references to the
<code>@vx</code> branch to the <code>@vx+1</code> branch.</p>
</blockquote>
</details>
<details>
<summary>Commits</summary>
<ul>
<li><a
href="https://github.com/jupyterhub/repo2docker-action/commit/00874a0abfebce00bab7eaa3332d3da603c5a2c2"><code>00874a0</code></a>
Merge pull request <a
href="https://redirect.github.com/jupyterhub/repo2docker-action/issues/116">#116</a>
from consideRatio/allow-tests-to-be-manually-triggered</li>
<li><a
href="https://github.com/jupyterhub/repo2docker-action/commit/1d1b9af136abe86d35b68ba6d0cfd6bbc71ed5af"><code>1d1b9af</code></a>
Allow tests to be manually triggered</li>
<li>See full diff in <a
href="https://github.com/jupyterhub/repo2docker-action/compare/b3cd89ff99f95b00abb5b4db27ec49bb4d3f8c85...00874a0abfebce00bab7eaa3332d3da603c5a2c2">compare
view</a></li>
</ul>
</details>
<br />
Dependabot will resolve any conflicts with this PR as long as you don't
alter it yourself. You can also trigger a rebase manually by commenting
`@dependabot rebase`.
[//]: # (dependabot-automerge-start)
[//]: # (dependabot-automerge-end)
---
<details>
<summary>Dependabot commands and options</summary>
<br />
You can trigger Dependabot actions by commenting on this PR:
- `@dependabot rebase` will rebase this PR
- `@dependabot recreate` will recreate this PR, overwriting any edits
that have been made to it
- `@dependabot merge` will merge this PR after your CI passes on it
- `@dependabot squash and merge` will squash and merge this PR after
your CI passes on it
- `@dependabot cancel merge` will cancel a previously requested merge
and block automerging
- `@dependabot reopen` will reopen this PR if it is closed
- `@dependabot close` will close this PR and stop Dependabot recreating
it. You can achieve the same result by closing it manually
- `@dependabot show <dependency name> ignore conditions` will show all
of the ignore conditions of the specified dependency
- `@dependabot ignore this major version` will close this PR and stop
Dependabot creating any more for this major version (unless you reopen
the PR or upgrade to it yourself)
- `@dependabot ignore this minor version` will close this PR and stop
Dependabot creating any more for this minor version (unless you reopen
the PR or upgrade to it yourself)
- `@dependabot ignore this dependency` will close this PR and stop
Dependabot creating any more for this dependency (unless you reopen the
PR or upgrade to it yourself)
</details>
Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>1 parent 1d6491f commit 2bed40c
1 file changed
+1
-1
lines changed| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
10 | 10 | | |
11 | 11 | | |
12 | 12 | | |
13 | | - | |
| 13 | + | |
14 | 14 | | |
15 | 15 | | |
16 | 16 | | |
0 commit comments