Skip to content

fix(ci): release notes referenced a nonexistent image tag - #3

Merged
igun997 merged 1 commit into
masterfrom
ci/fix-release-notes-image-tag
Aug 4, 2026
Merged

fix(ci): release notes referenced a nonexistent image tag#3
igun997 merged 1 commit into
masterfrom
ci/fix-release-notes-image-tag

Conversation

@igun997

@igun997 igun997 commented Aug 4, 2026

Copy link
Copy Markdown
Owner

Bug

docker/metadata-action strips the leading v from semver tags, so git tag v0.0.1 publishes images as 0.0.1. The v0.0.1 release notes told people to run:

docker pull ghcr.io/igun997/deploy-everything:v0.0.1   # does not exist

Confirmed against the published packages:

deploy-everything      latest, 0, 0.0, 0.0.1
deploy-everything-cli  latest, 0, 0.0, 0.0.1

Fix

  • meta job gains an image_tag output (${tag#v}), used in the release body. version still carries the full v0.0.1 for ldflags and the release title.
  • README tagging table corrected. My earlier note that 0.x.y gets no major-only tag was wrong — 0 is published. Also documented that image tags drop the v while version output keeps it.

The v0.0.1 release notes were edited by hand; this fixes it for every future tag.

Verified: release.yml parses as valid YAML, image_tag wired through to the release body.

docker/metadata-action strips the leading "v" from semver tags, so git tag
v0.0.1 publishes images as 0.0.1. Release notes printed
`docker pull ...:v0.0.1`, which does not exist. Add a meta.image_tag output
and use it in the release body.

Also correct the README tagging table: 0.x.y tags DO get a major-only `0`
tag (verified against the published v0.0.1 packages: latest, 0, 0.0, 0.0.1).
@coderabbitai

coderabbitai Bot commented Aug 4, 2026

Copy link
Copy Markdown

Warning

Review limit reached

@igun997, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 46 minutes

You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository.

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: 6adbde6b-88d1-43a8-b267-6e910d11f855

📥 Commits

Reviewing files that changed from the base of the PR and between f855983 and 764d511.

📒 Files selected for processing (2)
  • .github/workflows/release.yml
  • README.md

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@igun997
igun997 merged commit 24f6f79 into master Aug 4, 2026
4 checks passed
@igun997
igun997 deleted the ci/fix-release-notes-image-tag branch August 4, 2026 10:11
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