Skip to content

fix(release): correct the GHCR pull tag in Release notes#3

Merged
CryptoJones merged 1 commit into
mainfrom
ci/release-notes-tag
Jun 9, 2026
Merged

fix(release): correct the GHCR pull tag in Release notes#3
CryptoJones merged 1 commit into
mainfrom
ci/release-notes-tag

Conversation

@CryptoJones

Copy link
Copy Markdown
Owner

Summary

  • metadata-action's {{version}} publishes v-stripped image tags (git tag v1.1.0 → image :1.1.0), but the generated Release notes used github.ref_name (v1.1.0) in the docker pull commands — so the copy-paste pull on every Release page 404s.
  • Add a ver step that derives version=${GITHUB_REF_NAME#v} and reference :${{ steps.ver.outputs.version }} in the two pull lines. Release title stays v1.1.0.

Verified out-of-band: docker pull ghcr.io/cryptojones/osapplytrack-{api,poller}:1.1.0 and :latest pull clean anonymously; :v1.1.0 does not exist.

Test plan

  • release.yml parses; pull lines now reference the stripped version.
  • ci.yml runs green on this PR.
  • Verified live on the next v* tag (tag-only trigger; not exercised by this PR).

🤖 Generated with Claude Code

metadata-action's {{version}} publishes v-stripped image tags (tag v1.1.0 →
:1.1.0), but the generated Release notes used github.ref_name (v1.1.0) in the
docker pull commands, so the copy-paste pull 404'd on every Release page. Derive
a v-stripped version output and reference it in the pull lines.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
@CryptoJones CryptoJones merged commit 251240b into main Jun 9, 2026
2 checks passed
@CryptoJones CryptoJones deleted the ci/release-notes-tag branch June 9, 2026 07:01
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

Successfully merging this pull request may close these issues.

1 participant