Prepare main for 2.1 - #685
Open
heyitsaamir wants to merge 1 commit into
Open
Conversation
Preserve stable release lines under versioned branches and advance main's version metadata to 2.1.0. Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com> Copilot-Session: 2788417a-ae7e-4114-b254-4e639db57090
Contributor
There was a problem hiding this comment.
Pull request overview
This PR advances the repository’s versioning configuration to the 2.1 line and updates release-process documentation to support versioned maintenance branches (release/v<major>.<minor>) instead of a single release branch.
Changes:
- Updates
version.jsonto2.1.0and changespublicReleaseRefSpecto matchrelease/v<major>.<minor>branches via regex. - Updates
RELEASE.mdto base release/hotfix work on a configurableRELEASE_BRANCH(e.g.release/v2.0) and to target that branch in commands. - Adjusts guidance for major/minor bumps and release-note generation to align with versioned release branches.
Show a summary per file
| File | Description |
|---|---|
| version.json | Bumps the version to 2.1.0 and updates public release ref matching to release/v<major>.<minor> branches. |
| RELEASE.md | Updates release/hotfix instructions to use versioned release branches and a RELEASE_BRANCH variable throughout. |
Review details
Tip
Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
- Files reviewed: 2/2 changed files
- Comments generated: 2
- Review effort level: Lite
Comment on lines
104
to
+105
| - **Main branch**: `X.Y.Z-preview.1`, `X.Y.Z-preview.2`, etc. (prerelease, published with `next` npm tag) | ||
| - **Release branch**: `X.Y.Z`, etc. (stable, published with `latest` npm tag) | ||
| - **Versioned release branches** (`release/v<major>.<minor>`): `X.Y.Z`, etc. (stable, published with `latest` npm tag) |
Comment on lines
+18
to
+19
| - If `main` is still on the same major/minor development line, merge `origin/main` | ||
| - For an older maintained line, include only the intended backports; do not merge a newer development line |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Advances
mainto 2.1.0 while preserving the 2.0 train atrelease/v2.0.