Repository navigation
chore(release): candidate v2.0.19 - #228
Merged
Merged
Conversation
mega-maxwell
Bot
requested review from
Troublor,
flyq and
vincent-k2026
as code owners
September 30, 2026 05:59
Claude review status
🛠️ Review did not finish Attempted head This round did not publish: MODEL_ACTION_FAILED in phase review_retry. Anything listed below is from the last round that did. Re-run the workflow or push a new commit to try again. |
flyq
approved these changes
Sep 30, 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.
Release candidate v2.0.19 (was 2.0.15).
Cut from
917ce10654a75269291b3cc97842816c82b2708d, which is not the tip of the default branch:release-v2.0.19already exists at that commit, and merging this PR puts the version bump and the changelog entry on it. The default branch is left untouched — the next candidate syncs this entry back from the tag.It creates no tag; the tag is cut once, at settlement, by
release-settle→release-publish.Changelog: this release's entry drafted under
## v2.0.19(settle stamps the date on the release branch);previous release's entry synced from its tag: inserted.