Repository navigation
Conversation
Release PR #594 cut 2.0.0 but wrote its section as [2.1.0] with a compare link to a v2.1.0 tag that does not exist. It also omitted the breaking apps SDK change and everything released in the 2.0.0 rcs. - Retitle the section to 2.0.0, compare v1.12.0...v2.0.0, dated 2026-10-30 (the tag and GitHub release date) - Add a BREAKING CHANGES entry for #534 - Add the feat/fix/perf commits since 1.12.0 that the section missed, including #654 and #658 merged after the release PR was opened - Fold the hand-written "Unreleased" notes into 2.0.0; that code ships in the v2.0.0 tag, and release-please would otherwise insert future sections above it
This branch has not been deployed
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.
Summary
Release PR #594 cut 2.0.0 (tag
v2.0.0, GitHub release, PyPI), but the CHANGELOG section it wrote is headed[2.1.0]. Its compare link points atv2.1.0, a tag that doesn't exist. The section also leaves out the breaking apps SDK change and everything released in the 2.0.0 release candidates.This PR rewrites that one section:
[2.0.0], comparingv1.12.0...v2.0.0, dated 2026-10-30 (the date of the tag and the GitHub release).## Unreleasednotes into 2.0.0. That code ships in thev2.0.0tag. Left as is, release-please would put future release sections above "Unreleased".This is a one-time correction to a release that's already out. No release PR is open, so it can't conflict with release-please. The
choretype keeps it out of the next generated changelog. #656 adds a comment above the same top lines and may need a trivial rebase.Test plan
git archive v2.0.0(the only extra file is the generated_version.py, which reads2.0.0)git log v1.12.0..v2.0.0make quality-check: 2181 passed, 93.65% coverage