Cherry pick PR 3763: Bump version to 2.1 - #3764
Merged
Anusha Kolan (anushakolan) merged 1 commit intoAug 10, 2026
Merged
Conversation
## Why make this change? Bumps the product version to `2.1` in preparation for the next release. ## What is this change? Updates `<Version>` in `src/Directory.Build.props` from `2.0` to `2.1`. The release pipeline reads this value to stamp all build outputs and NuGet packages. ## How was this tested? - [ ] Integration Tests - [ ] Unit Tests No functional code changed; version string update only. Pipeline CI will validate that all projects build cleanly under the new version. ## Sample Request(s) N/A — no API or CLI behavior changed.
Copilot started reviewing on behalf of
Anusha Kolan (anushakolan)
August 10, 2026 17:50
View session
Contributor
There was a problem hiding this comment.
Pull request overview
Cherry-picks the version bump from main into release/2.1 so the build/release pipeline stamps outputs and NuGet packages with the upcoming 2.1 product version.
Changes:
- Updated the repository-wide
<Version>property from2.0to2.1insrc/Directory.Build.props.
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
RubenCerna2079
approved these changes
Aug 10, 2026
|
Azure Pipelines: Successfully started running 6 pipeline(s). |
Anusha Kolan (anushakolan)
enabled auto-merge (squash)
August 10, 2026 18:47
Aniruddh Munde (Aniruddh25)
approved these changes
Aug 10, 2026
Anusha Kolan (anushakolan)
deleted the
dev/anushakolan/cherry-pick-version-bump-2.1
branch
August 10, 2026 19:42
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.
Why make this change?
Cherry-pick of #3763 from
maintorelease/2.1to bump the product version in preparation for the 2.1 release.What is this change?
<Version>insrc/Directory.Build.propsfrom2.0to2.1.How was this tested?
No functional code changed; version string update only.
Sample Request(s)
N/A — no API or CLI behavior changed.