fix: restore version fields to 1.28.0 on develop - #1287
Conversation
The main->develop ancestry-reconciliation merge (-s ours, PR #1253) advanced the merge-base but used a zero-file-change merge, so develop's version fields were never updated to match main's actual v1.28.0 release. This left package.json, packages/suite/package.json, and sonar-project.properties at the stale 1.27.1 value, causing any branch cut from develop (e.g. hotfix/v1.28.1) to incorrectly regress main's version when merged. This brings develop's version fields in line with main (v1.28.0) so future release/hotfix branches inherit the correct base version. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
|
Warning Review limit reached
Next review available in: 14 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: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (3)
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 |
|
2 participants
Summary
Restore develop's stale version fields to
1.28.0in:package.jsonpackages/suite/package.jsonsonar-project.propertiesRoot cause
The main -> develop ancestry-reconciliation merge done with
-s oursin PR #1253 advanced the merge-base without bringing over the version-file changes from main. As a result, develop's release version fields stayed at1.27.1even though main had already releasedv1.28.0.That stale state then caused hotfix/v1.28.1 (branched from develop) to regress main's version metadata in PR #1285.
Why this PR
This PR brings develop's version fields back in line with main (
v1.28.0) so future release and hotfix branches inherit the correct base version.References