Repository navigation
Bump version to 2.3 - #3930
Merged
Aniruddh Munde (Aniruddh25) merged 2 commits intoNov 20, 2026
Merged
Bump version to 2.3#3930
Conversation
This was referenced Nov 19, 2026
aaronburtle
marked this pull request as ready for review
November 19, 2026 04:20
Contributor
There was a problem hiding this comment.
🟢 Approval recommended
There are no active review issues with the shared product version update to 2.2.
No open issues 🎉
What changed in this PR
Prepares Data API builder for the 2.2 release by updating the shared product version, addressing #3932. The corresponding release-branch change is covered by #3931.
Changes:
- Bumps
<Version>from2.1to2.2for release build and package versioning. - Makes no functional code changes.
| File | Description |
|---|---|
src/Directory.Build.props |
Updates the shared product version to 2.2. |
Review effort: Balanced
Souvik Ghosh (souvikghosh04)
approved these changes
Nov 19, 2026
RubenCerna2079
approved these changes
Nov 19, 2026
Aniruddh Munde (Aniruddh25)
deleted the
dev/aaronburtle/bump-version-2.2
branch
November 20, 2026 05:55
Aniruddh Munde (Aniruddh25)
pushed a commit
that referenced
this pull request
Nov 20, 2026
## Why make this change? - `release/2.2` was cut from `main` while `main` still had version 2.1. The release pipelines read the version from this branch, so it must say 2.2 before the Buddy and Official runs. - `main` moves to 2.3 separately in #3930. ## What is this change? - Updates `<Version>` in `src/Directory.Build.props` from `2.1` to `2.2` on `release/2.2`. - 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. ## Sample Request(s) N/A — no API or CLI behavior changed.
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?
release/2.2has been cut, somainmoves to the next development version, 2.3.mainstayed on 2.1 afterrelease/2.1was cut; this catches it up.release/2.2gets 2.2 through Bump version to 2.2 on release/2.2 #3931.What is this change?
<Version>insrc/Directory.Build.propsfrom2.1to2.3.How was this tested?
No functional code changed; version string update only.
Sample Request(s)
N/A — no API or CLI behavior changed.