fix(ci): release notes referenced a nonexistent image tag - #3
Conversation
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).
|
Warning Review limit reached
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 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 configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (2)
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. Comment |
Bug
docker/metadata-actionstrips the leadingvfrom semver tags, so git tagv0.0.1publishes images as0.0.1. The v0.0.1 release notes told people to run:docker pull ghcr.io/igun997/deploy-everything:v0.0.1 # does not existConfirmed against the published packages:
Fix
metajob gains animage_tagoutput (${tag#v}), used in the release body.versionstill carries the fullv0.0.1for ldflags and the release title.0.x.ygets no major-only tag was wrong —0is published. Also documented that image tags drop thevwhileversionoutput keeps it.The v0.0.1 release notes were edited by hand; this fixes it for every future tag.
Verified:
release.ymlparses as valid YAML,image_tagwired through to the release body.