Skip to content

fix(scripts/releaser): use the v-prefixed image tag in release notes - #31032

Open
denisra wants to merge 1 commit into
mainfrom
fix/releaser-image-tag
Open

denisra wants to merge 1 commit into
mainfrom
fix/releaser-image-tag

Conversation

@denisra

@denisra denisra commented Oct 19, 2026 •

Copy link
Copy Markdown
Collaborator

Problem

The release wizard writes this into every release's notes:

docker pull ghcr.io/coder/coder:2.37.5

but the workflow tags images with scripts/image_tag.sh, which always emits v<version>. ghcr.io/coder/coder:2.37.5 returns 404; ghcr.io/coder/coder:v2.37.5 is the real tag. Checked against v2.37.5, v2.37.4, v2.38.0 and v2.29.19 on ghcr.io: only the v-prefixed manifests exist.

release.go strips the v before formatting the tag (strings.TrimPrefix(newVersion.String(), "v")). The old bash generator used image_tag.sh directly and got it right.

Change

Format the tag with newVersion.String() (keeps the v), with a comment pointing at image_tag.sh as the source of truth.

Affected published notes (36 releases back to v2.29.19) can be fixed with gh release edit --notes-file; this PR only fixes future ones.

🤖 Generated with Claude Code

Part of ENT-224

The generated notes told users to `docker pull ghcr.io/coder/coder:2.37.5`,
but the release workflow tags images through scripts/image_tag.sh, which
always emits `v<version>`; the un-prefixed tag does not exist on ghcr.io
(404). Every release cut with the wizard carries the broken command.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
@linear-code

linear-code Bot commented Oct 19, 2026

Copy link
Copy Markdown

ENT-224

@denisra
denisra requested a review from f0ssel October 19, 2026 23:15

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant