Skip to content

chore: prepare SDK 3 and OTel 2 releases - #801

Open
zhongkechen wants to merge 2 commits into
refactor/per-invocation-plugin-instancesfrom
chore/prepare-python-major-release-20261021
Open

zhongkechen wants to merge 2 commits into
refactor/per-invocation-plugin-instancesfrom
chore/prepare-python-major-release-20261021

Conversation

@zhongkechen

@zhongkechen zhongkechen commented Oct 21, 2026 •

Copy link
Copy Markdown
Contributor

Prepare the next major release on top of #737 (refactor/per-invocation-plugin-instances). The stack includes its per-invocation plugin factories, coordinated Core/OTel migration, version bumps and dependency updates.

Versions in the stack

Package Version
Core SDK 3.0.0
OpenTelemetry 2.0.0
Extras 0.1.0
Testing 1.3.0

Core, OTel and Extras version changes are inherited from #737. Testing keeps the version published in the preceding minor release; its next version can be decided when the remaining release content is known.

Changes above #737

The two mainline commits above were merged after #737's last sync with main. Their patches are unchanged by the rebase. Overlapping version changes and compatibility checks already supplied by #737 are inherited from that PR.

Merge order and remaining scope

  1. Merge refactor(plugin): create one plugin instance per invocation #737 first.
  2. Retarget this PR to main and refresh the branch after that merge.
  3. Finalize any additional release content, package versions and release notes before publication.

This PR remains a draft while the release scope is being assembled.

Validation

Validation on Python 3.13 with #737 at 8ed1fb83 and this branch at 24add8b6:

  • 1,975 Core, metadata and conformance-template tests passed.
  • Built Core 3.0.0 and OTel 2.0.0 wheels passed all 736 OTel tests and 12 factory lifecycle compatibility cases.
  • The released-OTel rejection lane passed all four cases.
  • Core/OTel wheel and source-distribution builds, Hatch lint/format checks, commit-message validation and git diff --check passed.
  • git range-diff confirmed the two carried-forward mainline patches are unchanged.

Cloud and conformance runs are left to GitHub CI. Final release validation should include any further changes added to the stack.

@zhongkechen
zhongkechen force-pushed the chore/prepare-python-major-release-20261021 branch from dced913 to 24add8b Compare October 21, 2026 22:43
@zhongkechen
zhongkechen changed the base branch from main to refactor/per-invocation-plugin-instances October 21, 2026 22:43
@zhongkechen
zhongkechen added this pull request to stack #802 October 21, 2026 22:48
@zhongkechen
zhongkechen marked this pull request as ready for review October 21, 2026 22:49
@zhongkechen
zhongkechen deployed to ai-pr-review-runtime October 21, 2026 22:49 — with GitHub Actions Active
@zhongkechen
zhongkechen force-pushed the chore/prepare-python-major-release-20261021 branch from 24add8b to bd955be Compare October 21, 2026 22:49
@zhongkechen
zhongkechen deployed to ai-pr-review-runtime October 21, 2026 22:49 — with GitHub Actions Active
@github-actions

Copy link
Copy Markdown
Contributor

Codex AI review

No actionable findings. The added compatibility assertion matches the existing dependency range. Validation was limited to static inspection; tests were not run, per the review constraints.

Reviewed commit bd955be3889543878bc57e9184db20a03fd841e1. Workflow run

This branch was successfully deployed

1 active deployment
ai-pr-review-runtime — bd955be3 Deployed Oct 21, 2026 by zhongkechen via ai-pr-review / Codex review / Generate Codex review #2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant