chore(main): release 0.2.0#471
Conversation
Dependency Review✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.Scanned FilesNone |
|
Important Review skippedIgnore keyword(s) in the title. ⛔ Ignored keywords (2)
Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Organization UI Review profile: ASSERTIVE Plan: Pro Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
✨ Finishing Touches🧪 Generate unit tests (beta)
✨ Simplify code
📝 Coding Plan
Comment |
There was a problem hiding this comment.
Code Review
This pull request, generated by Release Please, prepares for version 0.2.0. However, it appears to be downgrading the version from the current 0.2.6, which is highly unusual. The main issue is in the CHANGELOG.md, where the git comparison URL for the new version is incorrect, making it difficult to see what changes are included in this release. This should be corrected to ensure the release is clear and accurate.
| @@ -1,5 +1,254 @@ | |||
| # Changelog | |||
|
|
|||
| ## [0.2.0](https://github.com/Aureliolo/synthorg/compare/v0.2.6...v0.2.0) (2026-03-15) | |||
There was a problem hiding this comment.
This pull request appears to be downgrading the project version from 0.2.6 to 0.2.0. This is highly unusual and could be unintentional.
The git comparison URL in the release heading is incorrect. It's .../compare/v0.2.6...v0.2.0, which will not show the changes included in this release because it's comparing a newer tag (v0.2.6) with what appears to be an older one (v0.2.0). The link should compare the new version against the previous logical release. Based on the project history, this is likely v0.1.4.
| ## [0.2.0](https://github.com/Aureliolo/synthorg/compare/v0.2.6...v0.2.0) (2026-03-15) | |
| ## [0.2.0](https://github.com/Aureliolo/synthorg/compare/v0.1.4...v0.2.0) (2026-03-15) |
|
Bogus PR — force-tag-creation requires release-please >= 17.2.0 (action v4.4.0 bundles 17.1.3). Tag v0.2.6 created manually. Workaround added in release.yml. |
Draft GitHub releases don't create git tags, and force-tag-creation requires release-please >= 17.2.0 (action v4.4.0 bundles 17.1.3). Without the tag, RP falls back to scanning all commits and computes a bogus version (e.g. 0.2.0 instead of 0.2.7). Add a pre-RP step that reads the manifest version and creates the tag if missing. Remove once googleapis/release-please-action#1187 ships. Also: created v0.2.6 tag manually and closed bogus PR #471.
## Summary - Add a pre-RP step to `release.yml` that reads the manifest version and creates the git tag if missing — draft GitHub releases don't create tags, and `force-tag-creation` requires RP >= 17.2.0 (action v4.4.0 bundles 17.1.3) - Update CLAUDE.md to document the workaround ## Context Every release produced a bogus `release 0.2.0` PR because RP couldn't find the latest release tag. Root cause: `force-tag-creation` flag is silently ignored in RP 17.1.3 (feature added in 17.2.0). Waiting on [googleapis/release-please-action#1187](googleapis/release-please-action#1187). Also done outside this PR: created `v0.2.6` tag manually, closed bogus PR #471. ## Test plan - [ ] Next release PR merge creates the tag before RP runs - [ ] RP finds the tag and does not produce a bogus version PR - [ ] Remove workaround step once action v4.4.1 ships
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #471 +/- ##
=======================================
Coverage 93.76% 93.76%
=======================================
Files 476 476
Lines 22616 22616
Branches 2180 2180
=======================================
Hits 21207 21207
Misses 1098 1098
Partials 311 311 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
🤖 I have created a release beep boop
0.2.0 (2026-03-15)
Features
Bug Fixes
Performance
Refactoring
Documentation
Tests
CI/CD
Maintenance
This PR was generated with Release Please. See documentation.