Repository navigation
ci(release): match release-please tags to the repo's vX.Y.Z tag format - #165
Conversation
release-please looked for family-office-v2.2.0, found nothing, and built the 2.3.0 release PR (#164) with a 172-entry changelog reaching back to the first commit. The repo tags releases as v2.2.0, v2.1.0, v2.0.0. Setting include-component-in-tag to false makes release-please find v2.2.0 and scope the changelog to the commits since it. Refs #112.
|
Codex usage limits have been reached for code reviews. Please check with the admins of this repo to increase the limits by adding credits. |
|
Warning Review limit reachedNext included review available in 11 minutes. View limit detailsLimit details: You’ve used all 2 included reviews currently available. You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. Review configuration: ⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Team Run ID: 📒 Files selected for processing (1)
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 |
Problem
The first release-please run with the new token opened #164, but its changelog has 172 entries reaching back to the first commit. The run log shows why:
Found release tag with component '', but not configured in manifest. release-please searched forfamily-office-v2.2.0; the repo's tags arev2.2.0,v2.1.0,v2.0.0, and v2.2.0 is already a published release.Fix
Set
include-component-in-tag: falseinrelease-please-config.jsonso tags arevX.Y.Z. On the next push to main, release-please will findv2.2.0and rebuild #164 with only the commits since it.Refs #112.
Changes made by Claude Fable 5.1 in Claude Code.