Skip to content

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

Closed
koppor opened this issue Apr 8, 2024 · 6 comments
Closed

Make ghcr.io/jbangdev/jbang-action:0.116.0 available #38

koppor opened this issue Apr 8, 2024 · 6 comments

Comments

@koppor
Copy link

koppor commented Apr 8, 2024

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

  /usr/bin/docker pull ghcr.io/jbangdev/jbang-action:0.116.0
  Error response from daemon: manifest unknown

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?

@jtama
Copy link

jtama commented Apr 12, 2024

Due to https://github.com/jbangdev/jbang-action/actions/runs/8505461801

@koppor
Copy link
Author

koppor commented Apr 12, 2024

Yeah, if there is no trust, there should be no release 🤣

=== RUN: Command Test: Does trust work
--- FAIL

Error: Expected string 'Adding .https://github.com/jruby. to /jbang/.jbang/trusted-sources.json' not found in error '[jbang] Trusting permanently: [https://github.com/jruby]

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]>
@koppor
Copy link
Author

koppor commented Jul 2, 2024

@jtama The linked build output is not available any more. Maybe, you could create it? (Maybe, you could also check #39 ^^)

@jtama
Copy link

jtama commented Jul 2, 2024

Sorry i can't do anything on this repository/

@maxandersen Could you please re-launch the release process.

@maxandersen
Copy link
Collaborator

i missed this - releasing 0.117 - should let us see where in the release chain things goes wrong (if still issue)

@koppor
Copy link
Author

koppor commented Jul 8, 2024

Worked fine with 0.177.1 - koppor/github-contributors-list#21

Thus closing this as obsolete.

@koppor koppor closed this as not planned Won't fix, can't repro, duplicate, stale Jul 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants