-
Notifications
You must be signed in to change notification settings - Fork 11
Make ghcr.io/jbangdev/jbang-action:0.116.0 available #38
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
This was referenced Apr 8, 2024
Yeah, if there is no trust, there should be no release 🤣
|
nscuro
added a commit
to DependencyTrack/hyades
that referenced
this issue
Apr 16, 2024
The Docker image for v0.116.0 is not available yet jbangdev/jbang-action#38 Signed-off-by: Niklas <[email protected]>
This was referenced Apr 25, 2024
Closed
Sorry i can't do anything on this repository/ @maxandersen Could you please re-launch the release process. |
i missed this - releasing 0.117 - should let us see where in the release chain things goes wrong (if still issue) |
Worked fine with 0.177.1 - koppor/github-contributors-list#21 Thus closing this as obsolete. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
At https://github.com/jbangdev/jbang-action/releases/tag/v0.116.0, there is a tag. This causes dependabot filing a pull request. Example: gi-ev/LNI#167
I get following output
I checked https://github.com/jbangdev/jbang-action/releases, but there is no 0.116.0 release.
At https://github.com/orgs/jbangdev/packages/container/package/jbang-action, there is no package for 0.116.0.
Would it be possible to publish the release 0.116.0 also as package?
The text was updated successfully, but these errors were encountered: