fix(release): repin patch-release-me to 0.6.5 (0.6.6's GHCR image was never published)#168
Merged
Merged
Conversation
…s never published 42ByteLabs/patch-release-me's 0.6.6 git tag/release exists (published 2026-05-25), but its container image was never pushed to ghcr.io - confirmed via anonymous registry query (ghcr.io/v2/42bytelabs/patch-release-me/tags/list) showing only 0.6.5 and earlier tags actually exist. This broke both update-release.yml and the new release_bump step in update-codeql-version.yml, both of which pinned the 0.6.6 commit SHA - every run failed at 'Build 42ByteLabs/patch-release-me@...' with 'ghcr.io/42bytelabs/patch-release-me:0.6.6: not found'. Repinned both workflows to 0.6.5's commit SHA. action.yml is byte-identical between 0.6.5 and 0.6.6 (confirmed via GitHub API blob SHA comparison), so this is a safe, no-behavior-change repin. Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
Contributor
There was a problem hiding this comment.
Pull request overview
This PR fixes broken release workflows by repinning the 42ByteLabs/patch-release-me GitHub Action from the 0.6.6 commit (whose GHCR image is missing) back to the 0.6.5 commit, restoring a pullable container image while keeping action behavior unchanged.
Changes:
- Repin
update-release.ymlto42ByteLabs/patch-release-me@431a8279...(0.6.5). - Repin
update-codeql-version.yml’s optionalrelease_bumpstep to the same0.6.5commit SHA.
Show a summary per file
| File | Description |
|---|---|
| .github/workflows/update-release.yml | Repins patch-release-me to the 0.6.5 commit SHA to avoid the missing 0.6.6 GHCR image. |
| .github/workflows/update-codeql-version.yml | Repins the optional release_bump step to the same 0.6.5 commit SHA for consistency and reliability. |
Review details
Tip
Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
- Files reviewed: 2/2 changed files
- Comments generated: 0
- Review effort level: Low
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
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.
What broke
Dispatching
update-release.yml(mode: patch) just now to publish the CLI 2.21.4 bump failed immediately:Confirmed the root cause is upstream:
42ByteLabs/patch-release-me's0.6.6git tag/release exists (published 2026-05-25), but the corresponding container image was apparently never pushed to GHCR. Verified via an anonymous GHCR registry API query (GET https://ghcr.io/v2/42bytelabs/patch-release-me/tags/list) — only0.6.5and earlier tags actually exist as real images;0.6.6/v0.6.6are absent.This broke both workflows that use this action, since both pinned the
0.6.6commit SHA:update-release.yml(pre-existing, unrelated to recent work here)update-codeql-version.yml's new optionalrelease_bumpstep (feat(update-codeql-version): add optional release_bump input to publish in the same PR #167, merged today)Fix
Repin both to
0.6.5's commit SHA (431a82795eda94d09b3821da9391c53ab287e84d), which does have a real, pullable image. Confirmedaction.ymlis byte-identical between0.6.5and0.6.6(same blob SHA via the GitHub API) — samemodeinput, same Docker entrypoint/args — so this is a safe, no-behavior-change repin, not a downgrade in functionality.Verification
gh api repos/42ByteLabs/patch-release-me/git/refs/tags/0.6.5→ confirms the commit SHA.0.6.5/v0.6.5images exist;0.6.6/v0.6.6do not.action.ymlcontent (via GitHub API blob SHA) is identical at both refs.Next step after merge
Re-dispatch
update-release.yml(mode: patch) to actually publish the pending CLI 2.21.4 changes.Co-authored-by: Copilot App 223556219+Copilot@users.noreply.github.com