chore(main): release 6.1.0-beta.1#834
Merged
Merged
Conversation
bokelley
previously approved these changes
May 23, 2026
Contributor
bokelley
left a comment
There was a problem hiding this comment.
Release PR generated by Release Please for 6.1.0-beta.1.
Contributor
There was a problem hiding this comment.
LGTM. Standard release-please train — 6.0.0-beta.1 → 6.1.0-beta.1, picking up the webhook URL policy / wholesale feed sender feat from 65f84d2. CHANGELOG, manifest, and version stamp only; no source touched.
Things I checked
- Diff is exactly the three release-please-managed files (
.release-please-manifest.json,CHANGELOG.md,pyproject.toml). No source undersrc/adcp/**modified. - Version bump is consistent across all three: manifest
6.0.0-beta.1 → 6.1.0-beta.1, changelog entry matches,pyproject.tomlmatches the manifest. - Conventional-commit signal is intact: the underlying
feat:on 65f84d2 maps to a minor bump on a0.x/beta train (6.0 → 6.1), no!orBREAKING CHANGE:footer, so a minor is the right shape. - Label is
autorelease: pending— not in the label-hold set.
Follow-ups (non-blocking — file as issues)
pyproject.tomlversion string moved from the PEP 440 canonical6.0.0b1to the non-canonical6.1.0-beta.1. It's still valid PEP 440 (normalizes to6.1.0b1on the wire), butpipandtwinewill emit non-canonical-version warnings on every build/upload. Worth pinning therelease-please-config.jsonversion-fileextractor (or thepyproject.tomlstrategy) to emit the canonical6.1.0b1form so the source-of-truth matches what PyPI stores. Notable that the prior release landed canonical and this one drifted — likely the manifest re-derivation path.
Safe to merge once release-please CI is green.
2 tasks
Contributor
There was a problem hiding this comment.
LGTM. Release-please-generated, three files, all the right shape.
Things I checked
- Version bump is coherent across the three files:
.release-please-manifest.jsonandCHANGELOG.mdcarry the semver form6.1.0-beta.1;pyproject.tomlcarries the PEP 440 form6.1.0b1. That's the standing convention — release-please writes semver, PEP 440 demands the squashed form on the wire to PyPI. - The
chore: normalize prerelease version to PEP 440commit is exactly the manual fixup that release-please's prerelease tracking needs on this repo. Not new behavior. - Underlying feature commit
feat: add webhook URL policy and wholesale feed sender(65f84d2) is a non-breakingfeat:— minor bump from6.0.0-beta.1to6.1.0-beta.1matches. No!orBREAKING CHANGE:footer expected. - No source changes.
src/adcp/**,tests/**,schemas/**all untouched. Public API surface unchanged.
Safe to merge once CI is green — merging publishes to PyPI via the release-please post-merge job.
bokelley
approved these changes
May 23, 2026
Contributor
bokelley
left a comment
There was a problem hiding this comment.
Release PR checks are green for 6.1.0-beta.1.
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
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.1.0-beta.1 (2026-05-23)
Features
This PR was generated with Release Please. See documentation.