Cut the tag with a tool the tagging job actually has - #177
Merged
Conversation
The manifest step called bun. That job checks out without credentials and installs no toolchain on purpose, so bun is not there: it failed with 'command not found' after the image had already been pushed to ghcr, which is the one point in a release where a failure leaves a published image and no tag pointing at it. jq is on the runner and produces the same document.
davidmckayv
requested review from
MikeRyanDev,
guidovizoso and
tylerslaton
as code owners
August 22, 2026 18:28
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
v0.0.2pushed its image and then died onbun: command not foundin Write the image manifest. That job checks out withpersist-credentials: falseand installs no toolchain by design, sobunwas never going to be there. The failure lands after the image is pushed, which is the worst place for it: a published image with no tag and no release.jqis preinstalled on the runner and emits the same manifest, byte for byte, so the job stays credential-free and toolchain-free.Separately,
Open the release PRinrelease.ymlfailed withGitHub Actions is not permitted to create or approve pull requests. That is a repository setting, not code. It is now enabled, so the next release opens its own PR.