chore(main): release 6.0.0-beta.1#817
Merged
Merged
Conversation
Merged
2 tasks
github-actions
Bot
changed the title
github-actions
Bot
force-pushed
the
release-please--branches--main
branch
2 times, most recently
from
36a714b to
561f4c7
Compare
|
The automated review encountered an issue (possibly reached max turns, timed out, or failed to post the final This is an automated message from the Argus AI review workflow. |
2 tasks
github-actions
Bot
force-pushed
the
release-please--branches--main
branch
from
3e0f7e1 to
543c3ac
Compare
![aao-ipr-bot[bot]](https://avatars.githubusercontent.com/u/134922?s=60&v=4){kind=small}
There was a problem hiding this comment.
LGTM. Release-please did the right thing on the manifest; bokelley's normalization commit makes the wheel installable. Approving.
Things I checked
.release-please-manifest.jsonstays at6.0.0-beta.1(semver) — correct, that's the value release-please diffs against for the next bump.pyproject.tomlat6.0.0b1(PEP 440 normalized) — PyPI rejects6.0.0-beta.1directly, so the normalization is load-bearing for the publish step.release-type: python+prerelease: true+prerelease-type: betainrelease-please-config.jsonis the documented config that produces the semver form release-please writes topyproject.toml. The manual fix-up is the known workaround.- CHANGELOG content matches the commits since
v5.7.0: #829 (feat), #811 (fix), #823/#828 (docs). No!orBREAKING CHANGE:footer in any of them — version jumps to 6.0 because the v6 beta line was opened intentionally (MIGRATION_v5_to_v6 stub landed in #823), not from a conventional-commit semver signal. Right call. - No code, no public-API surface, no generated types. Skip-everything rules apply — no expert delegation needed.
Follow-ups (non-blocking — file as issues)
- Every future beta release PR will hit the same
6.0.0-beta.N→6.0.0bNnormalization. Either acustomize-versionextension or anextra-filespost-processor inrelease-please-config.jsonwould make this automatic. Two manual fix-up commits in a row is a pattern; three would be a problem.
Safe to merge once CI is green.
Contributor
Author
|
🤖 Created releases: 🌻 |
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
1 participant
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.
🤖 I have created a release beep boop
6.0.0-beta.1 (2026-05-23)
Features
Bug Fixes
Documentation
This PR was generated with Release Please. See documentation.