[Johnathan W (j7nw4r)]

Summary

Prepare the Event Hubs family beta releases with the planned date 2026-11-06.

Motivation

The family release includes the message annotation fix from #7429 and the producer discovery cleanup fix from #7511. The Event Hubs ports must require the releases that contain these fixes.

Changes

• Finalize the notes for azure-core-amqp 1.0.0-beta.14 and azure-messaging-eventhubs 1.0.0-beta.16.
• Record azure-messaging-eventhubs-checkpointstore-blob 1.0.0-beta.5 as a dependency-only release.
• Require AMQP 1.0.0-beta.14 in both Event Hubs ports and Event Hubs 1.0.0-beta.16 in the checkpoint store port.
• Keep the planned package versions and the existing Core and Storage minimums. Keep Rust cancellation and concurrent cleanup deferred to [AMQP] Complete session cleanup after management and discovery failures azure-sdk-for-rust#5527.

The release follows the guidance in #7425. The dependency minimums above use the versions being released. The headers keep these versions until the release tags exist.

• Obtain release authorization. Approve only the AMQP, Event Hubs, and checkpoint store package stages. Deny unrelated package stages, including Core and OpenTelemetry.
• Publish AMQP, Event Hubs, and the checkpoint store in that order. Run shared vcpkg branch updates one package at a time.
• Make sure each release tag points to the approved release commit before merging its version-increment PR.
• Review the automation PRs titled Increment version for ... releases. Make sure they update both src\private\package_version.hpp and CHANGELOG.md to the next versions below. Merge them promptly after their release tags exist, their CI passes, and a maintainer approves.

Package	Release version	Next version with an Unreleased entry
azure-core-amqp	1.0.0-beta.14	1.0.0-beta.15
azure-messaging-eventhubs	1.0.0-beta.16	1.0.0-beta.17
azure-messaging-eventhubs-checkpointstore-blob	1.0.0-beta.5	1.0.0-beta.6

The release pipeline runs Update-PkgVersion.ps1 without -NewVersionString to create these increments. Its version-increment job depends on the release gate and can run before tag creation finishes. Hold each merge until the tag exists. Keep the published dependency minimums at AMQP beta.14 and Event Hubs beta.16.

Validation

Release preparation restored the three Unreleased entries and ran these repository commands in the release worktree. Each command returned exit code 0.

pwsh -NoLogo -NoProfile -File .\eng\scripts\Update-PkgVersion.ps1 -RepoRoot 'C:\Repos\azure-sdk-for-cpp-eventhubs-family-release' -ServiceDirectory core -PackageName azure-core-amqp -NewVersionString 1.0.0-beta.14 -ReleaseDate 2026-11-06 -Verbose
pwsh -NoLogo -NoProfile -File .\eng\scripts\Update-PkgVersion.ps1 -RepoRoot 'C:\Repos\azure-sdk-for-cpp-eventhubs-family-release' -ServiceDirectory eventhubs -PackageName azure-messaging-eventhubs -NewVersionString 1.0.0-beta.16 -ReleaseDate 2026-11-06 -Verbose
pwsh -NoLogo -NoProfile -File .\eng\scripts\Update-PkgVersion.ps1 -RepoRoot 'C:\Repos\azure-sdk-for-cpp-eventhubs-family-release' -ServiceDirectory eventhubs -PackageName azure-messaging-eventhubs-checkpointstore-blob -NewVersionString 1.0.0-beta.5 -ReleaseDate 2026-11-06 -Verbose

Update-PkgVersion.ps1 called eng\common\scripts\Update-ChangeLog.ps1 for each package. Confirm-ChangeLogEntry -ForRelease $true -SantizeEntry removed the empty release sections. Verify-ChangeLog.ps1 and Get-PkgVersion.ps1 passed for all three packages.

The generated changelogs and version headers match commit 7d568bfb0e5cc7f7026922d251da313d8d9af19e after Git line-ending normalization. This replay required no further source commit. The worktree log out\release-validation\script-redo.log records the input headings, commands, output, and exit codes.

• The Event Hubs resource tests passed all 14 tests. git diff --check passed.
• The generated vcpkg manifests contain the planned package versions and updated minimums.
• All three production libraries, both Event Hubs test executables, and four public Event Hubs samples compiled and linked in Windows Release mode with Rust disabled. The build uses released Core 1.16.4, Identity 1.13.0, Storage Common 12.15.0, and Storage Blobs 12.19.1.
• All 40 native uAMQP tests passed. Selected offline Event Hubs regressions passed 95 of 96 tests. PropertiesCleanupDeathTest.ManagementCloseFailureStillEndsSession failed and reproduced in all three isolated repeats. Two repeats aborted with Could not end session; the other exited with status 1.
• The cleanup failure comes from baseline mock-server teardown. A diagnostic wrapper captured SessionImpl::End throwing through AmqpServerMock::StopListening, followed by another throw from its destructor. The mock tries to end a session after its peer connection closes. The stack reproduced in ten isolated localhost repeats. This PR changes metadata only.
• The general AMQP test executable failed to compile at sdk\core\azure-core-amqp\test\ut\session_cleanup_tests.cpp:103. Nested GoogleTest exception assertions generate duplicate labels inside EXPECT_EXIT. A minimal reproduction fails with both MSVC preprocessing modes. Moving the assertions into a helper compiles in both modes. This test source matches the pinned main commit.
• The internal AMQP sample path-length failure was environmental. The sample compiled and linked at the shorter build path C:\Repos\eh7532-build. The release-preparation commit still changes metadata only.
• Live tests need the Event Hubs resource settings and Azure credentials. The local environment lacks them.
• API approval status remains unverified. The MCP release-readiness tool does not support C++, and the API review services lack authenticated access.
• Core CI build 7047968 passed after the retry of the failed LiveTest_Public stage, with successful jobs excluded. The build completed at 2026-11-06T18:52:47Z. The original failure came from vcpkg z-applocal for json-test-readme.exe, with exit code 5.
• All 291 PR checks completed with 290 successful and one skipped. None remain pending or failed.
• The release-preparation PR is ready for review. The local test failures above, full live end-to-end testing, and API approval remain release gates. This draft does not authorize publishing.

The base commit is 8021f71052bbf87ccf1c2b470e2af436d37c86ff. A maintainer must approve the release scope and make sure the changelog date matches the actual release date before shipping.

[azure-pipelines]

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.

[Copilot]

🔵 Needs a closer look

Maintainer judgment is needed to authorize the three-package release and assess release gates involving unverified API approval, unavailable live end-to-end validation, and unresolved native AMQP test compilation and cleanup failures.

No open issues 🎉

What changed in this PR

Prepares the November Event Hubs family beta releases through metadata-only changes, aligning dependency minimums with the releases containing the AMQP annotation and producer cleanup fixes.

Changes:

• Finalizes the three package changelogs with the planned release date of 2026-11-06.
• Requires AMQP 1.0.0-beta.14 in both Event Hubs ports and Event Hubs 1.0.0-beta.16 in the checkpoint store port.
• Documents checkpoint store beta.5 as a dependency-only release, preserving package versions and existing Core and Storage minimums.

File	Description
sdk/​eventhubs/​azure-messaging-eventhubs/​vcpkg/​vcpkg.json	Raises the AMQP minimum to beta.14.
sdk/​eventhubs/​azure-messaging-eventhubs/​CHANGELOG.md	Finalizes beta.16 notes and records the AMQP dependency update.
sdk/​eventhubs/​azure-messaging-eventhubs-checkpointstore-blob/​vcpkg/​vcpkg.json	Raises AMQP and Event Hubs dependency minimums.
sdk/​eventhubs/​azure-messaging-eventhubs-checkpointstore-blob/​CHANGELOG.md	Finalizes beta.5 as a dependency-only release.
sdk/​core/​azure-core-amqp/​CHANGELOG.md	Finalizes beta.14 notes and removes empty sections.

_{Review effort: Balanced}