Repository navigation
chore: sync main into development after v0.11.1; open 0.11.2rc1 - #1067
Merged
Merged
Conversation
Release v0.11.1 — Fail Closed (Windows fix before publishing)
…1066) Bring back the merge commit of the v0.11.1 release pull request so main carries no commit development lacks.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
Note The title starts with
|
|
Sorry @cemililik, you've used your own review budget of 250,000 diff characters for the last 7 days. You can request another review in 21 hours and 7 minutes by commenting |
Contributor
|
Note Currently processing new changes in this PR. This may take a few minutes, please wait... ⚙️ Run configuration
📒 Files selected for processing: 1
✨ Finishing Touches
Comment |
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
Post-release sync for v0.11.1. It brings
main's release merge commit back intodevelopment, asdocs/standards/release.mdrequires after every release, and opens the next development cycle. Merge with "Create a merge commit", so the sync keeps its second parent.Related issues
None.
Changes
a4e1d1a. Mergesmain(2636b5c, the Release v0.11.1 — Fail Closed (Windows fix before publishing) #1066 merge commit thatv0.11.1points to) intodevelopment. No file changes, somaincarries no commit thatdevelopmentlacks.7527a78. Bumpspyproject.tomlfrom0.11.1to0.11.2rc1, the next development cycle (precedent:6335dc2afterv0.11.0).CHANGELOG.mdalready has the empty[Unreleased]section. Thercmarker is not a version promise: the next cycle's tag is still derived at the cut from the bump table.Type
Testing
check_notebook_pins,check_release_record_sync,check_deprecation_targets,check_site_claimsandupdate_site_version --checkall pass with thercversion. The notebooks and the site keep0.11.1, the latest release.🤖 Generated with Claude Code
Summary by CodeRabbit