chore(main): release 6.3.0-beta.4#870
Merged
Merged
Conversation
bokelley
changed the title
bokelley
force-pushed
the
release-please--branches--main
branch
from
cbda59a to
77751c0
Compare
github-actions
Bot
force-pushed
the
release-please--branches--main
branch
from
77751c0 to
c0cfe35
Compare
bokelley
changed the title
bokelley
previously approved these changes
May 26, 2026
Contributor
bokelley
left a comment
bokelley
left a comment
There was a problem hiding this comment.
Release metadata and diff match 6.3.0-beta.4.
github-actions
Bot
force-pushed
the
release-please--branches--main
branch
from
9e05814 to
6c0c200
Compare
bokelley
approved these changes
May 26, 2026
Contributor
bokelley
left a comment
bokelley
left a comment
There was a problem hiding this comment.
Refreshed release diff still matches 6.3.0-beta.4; PEP 440 pyproject version is correct.
There was a problem hiding this comment.
LGTM. Release-please bump from 6.2.0-beta.4 to 6.3.0-beta.4, picking up #876 (externally managed webhook signing capabilities).
Things I checked
- Manifest version (
.release-please-manifest.json) andpyproject.tomlversion agree. - PEP 440 normalization:
6.3.0-beta.4→6.3.0b4. Correct. - CHANGELOG entry links to the right compare range and the right commit (
3c312a0). - Single
feat:in the window, no breaking-change markers — minor bump is the right shape.
Safe to merge.
There was a problem hiding this comment.
LGTM. Standard release-please autorelease PR — version bumps and CHANGELOG entry only, no source code change.
Things I checked
.release-please-manifest.jsonbump (6.2.0-beta.4 → 6.3.0-beta.4) matches the CHANGELOG header atCHANGELOG.md:3.pyproject.toml:7PEP 440 normalization (6.3.0b4) is the correct form of the same version — matches the normalize-prerelease commit2c05cd8.- Single CHANGELOG entry points at #876 (externally managed webhook signing capabilities), landed via
3c312a0. Semver bump isfeat:→ minor, correct. - No source files touched; no public-API audit, generated-type audit, or expert delegation needed.
The third commit (chore: trigger release CI) is the only non-bot one — re-kick of CI, fine.
Safe to merge.
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.3.0-beta.4 (2026-05-26)
Features
This PR was generated with Release Please. See documentation.