Fix version link formatting in CHANGELOG.md#2263
Conversation
Corrected the link format for version comparison.
WalkthroughUpdated two CHANGELOG.md compare links for the 16.2.0.rc.0 entry: removed the leading "v" from the left-side version in the URL path (changed Changes
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~2 minutes Possibly related PRs
Suggested labels
Suggested reviewers
Poem
Pre-merge checks and finishing touches✅ Passed checks (3 passed)
✨ Finishing touches🧪 Generate unit tests (beta)
📜 Recent review detailsConfiguration used: Organization UI Review profile: CHILL Plan: Pro 📒 Files selected for processing (1)
✅ Files skipped from review due to trivial changes (1)
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (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 |
Code ReviewThank you for the PR! I've reviewed the changes and have the following feedback: 🔍 Issue AnalysisThe PR changes line 1876 from: to: The change removes the ✅ What's Correct
|
PR #1856 unintentionally introduced a `v` prefix to git tags when it replaced `release-it` with manual git commands. The `release-it` tool auto-detected the existing tag format (no `v` prefix), but the manual implementation explicitly added `v#{version}`. This broke 9+ years of consistent tagging convention (versions 2.0.0 through 16.1.2 all used no `v` prefix) and caused issues like broken CHANGELOG links (fixed in PR #2263). Changes: - Remove `v` prefix from tag creation in release.rake - Update releasing.md to document the correct convention - Update update-changelog.md to reflect no `v` prefix for future tags - Add notes about historical v16.2.0.beta.x tags that have `v` prefix Fixes #2267 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Opus 4.5 <[email protected]>
The tag v16.1.1 does not exist - only 16.1.1 exists (without v prefix). This is the same fix as the previous commit but for react_on_rails_pro/CHANGELOG.md. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Opus 4.5 <[email protected]>
PR #1856 unintentionally introduced a `v` prefix to git tags when it replaced `release-it` with manual git commands. The `release-it` tool auto-detected the existing tag format (no `v` prefix), but the manual implementation explicitly added `v#{version}`. This broke 9+ years of consistent tagging convention (versions 2.0.0 through 16.1.2 all used no `v` prefix) and caused issues like broken CHANGELOG links (fixed in PR #2263). Changes: - Remove `v` prefix from tag creation in release.rake - Update releasing.md to document the correct convention - Update update-changelog.md to reflect no `v` prefix for future tags - Add notes about historical v16.2.0.beta.x tags that have `v` prefix Fixes #2267 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Opus 4.5 <[email protected]>
PR #1856 unintentionally introduced a `v` prefix to git tags when it replaced `release-it` with manual git commands. The `release-it` tool auto-detected the existing tag format (no `v` prefix), but the manual implementation explicitly added `v#{version}`. This broke 9+ years of consistent tagging convention (versions 2.0.0 through 16.1.2 all used no `v` prefix) and caused issues like broken CHANGELOG links (fixed in PR #2263). Changes: - Remove `v` prefix from tag creation in release.rake - Update releasing.md to document the correct convention - Update update-changelog.md to reflect no `v` prefix for future tags - Add notes about historical v16.2.0.beta.x tags that have `v` prefix Fixes #2267 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Opus 4.5 <[email protected]>
Corrected the link format for version comparison.
Summary
Remove this paragraph and provide a general description of the code changes in your pull
request... were there any bugs you had fixed? If so, mention them. If
these bugs have open GitHub issues, be sure to tag them here as well,
to keep the conversation linked together.
Pull Request checklist
Remove this line after checking all the items here. If the item is not applicable to the PR, both check it out and wrap it by
~.Add the CHANGELOG entry at the top of the file.
Other Information
Remove this paragraph and mention any other important and relevant information such as benchmarks.
Summary by CodeRabbit
Note: This release contains no new features, bug fixes, or functional changes visible to end-users.
✏️ Tip: You can customize this high-level summary in your review settings.