Fix version number increments after releases - #7425
Merged
Merged
Conversation
This was referenced Sep 18, 2026
|
Azure Pipelines: Successfully started running 3 pipeline(s). 7 pipeline(s) were filtered out due to trigger conditions. There may be pipelines that require an authorized user to comment /azp run to run. |
This was referenced Sep 18, 2026
Copilot started reviewing on behalf of
Anton Kolesnyk (antkmsft)
September 18, 2026 19:23
View session
Contributor
There was a problem hiding this comment.
🟢 Approval recommended
The package versions, changelogs, and dependency minimums are consistent.
Pull request overview
Advances post-release package versions and aligns checkpoint-store dependencies with released versions.
Changes:
- Increment Event Hubs, checkpoint store, and AMQP prerelease versions.
- Add matching unreleased changelog sections.
- Raise checkpoint-store dependency minimums.
File summaries
| File | Description |
|---|---|
| sdk/eventhubs/azure-messaging-eventhubs/src/private/package_version.hpp | Advances Event Hubs to beta.16. |
| sdk/eventhubs/azure-messaging-eventhubs/CHANGELOG.md | Adds the beta.16 unreleased section. |
| sdk/eventhubs/azure-messaging-eventhubs-checkpointstore-blob/vcpkg/vcpkg.json | Updates dependency minimum versions. |
| sdk/eventhubs/azure-messaging-eventhubs-checkpointstore-blob/src/private/package_version.hpp | Advances checkpoint store to beta.5. |
| sdk/eventhubs/azure-messaging-eventhubs-checkpointstore-blob/CHANGELOG.md | Adds the beta.5 unreleased section. |
| sdk/core/azure-core-amqp/src/private/package_version.hpp | Advances AMQP core to beta.14. |
| sdk/core/azure-core-amqp/CHANGELOG.md | Adds the beta.14 unreleased section. |
Review details
- Files reviewed: 7/7 changed files
- Comments generated: 0
- Review effort level: Balanced
💡 Add a code-review agent skill for context-aware, tailored reviews. Learn more in the docs.
Anton Kolesnyk (antkmsft)
marked this pull request as ready for review
September 18, 2026 19:25
Anton Kolesnyk (antkmsft)
requested review from
Larry Osterman (LarryOsterman),
Rick Winter (RickWinter),
Josue Gomez (SwayGom),
Ashish Chhabria (axisc),
Eric Lam (MSFT) (hmlam),
Johnathan W (j7nw4r),
Amit Bhatia (meetamitbhatia),
Sagar Patel (sagar0207),
SJ (sjkwak) and
Jeff Fisher (xirzec)
as code owners
September 18, 2026 19:26
|
Azure Pipelines: Successfully started running 3 pipeline(s). 7 pipeline(s) were filtered out due to trigger conditions. There may be pipelines that require an authorized user to comment /azp run to run. |
Anton Kolesnyk (antkmsft)
enabled auto-merge (squash)
September 18, 2026 19:30
Johnathan W (j7nw4r)
approved these changes
Sep 18, 2026
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.
To avoid problems in versioning (see linked PRs), do the following:
Before you release, if you depend on a newer version of a library, update
vcpkg/vcpkg.json.When you do the release, in the release pipeline, only approve the packages that you are releasing. I.e. if you're only releasing
azure-core-amqp-cpp, do NOT approveazure-core-cppandazure-core-opemtelemetry-cpp. You can deny them right away to avoid any misclicks.After the release release automation creates a PR, called "Increment version for ... releases" (see linked PRs below). Approve and merge it right after the release (after release tag has been created, to be exact - https://github.com/Azure/azure-sdk-for-cpp/tags).