Skip to content

chore(main): release 6.1.0-beta.1#834

Merged
bokelley merged 3 commits into
mainfrom
release-please--branches--main
May 23, 2026
Merged

chore(main): release 6.1.0-beta.1#834
bokelley merged 3 commits into
mainfrom
release-please--branches--main

Conversation

@github-actions
Copy link
Copy Markdown
Contributor

🤖 I have created a release beep boop

6.1.0-beta.1 (2026-05-23)

Features

  • add webhook URL policy and wholesale feed sender (65f84d2)

This PR was generated with Release Please. See documentation.

bokelley
bokelley previously approved these changes May 23, 2026
Copy link
Copy Markdown
Contributor

@bokelley bokelley left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Release PR generated by Release Please for 6.1.0-beta.1.

aao-ipr-bot[bot]
aao-ipr-bot Bot previously approved these changes May 23, 2026
Copy link
Copy Markdown
Contributor

@aao-ipr-bot aao-ipr-bot Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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 under src/adcp/** modified.
  • Version bump is consistent across all three: manifest 6.0.0-beta.1 → 6.1.0-beta.1, changelog entry matches, pyproject.toml matches the manifest.
  • Conventional-commit signal is intact: the underlying feat: on 65f84d2 maps to a minor bump on a 0.x/beta train (6.0 → 6.1), no ! or BREAKING 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.toml version string moved from the PEP 440 canonical 6.0.0b1 to the non-canonical 6.1.0-beta.1. It's still valid PEP 440 (normalizes to 6.1.0b1 on the wire), but pip and twine will emit non-canonical-version warnings on every build/upload. Worth pinning the release-please-config.json version-file extractor (or the pyproject.toml strategy) to emit the canonical 6.1.0b1 form 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.

Copy link
Copy Markdown
Contributor

@aao-ipr-bot aao-ipr-bot Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM. Release-please-generated, three files, all the right shape.

Things I checked

  • Version bump is coherent across the three files: .release-please-manifest.json and CHANGELOG.md carry the semver form 6.1.0-beta.1; pyproject.toml carries the PEP 440 form 6.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 440 commit 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-breaking feat: — minor bump from 6.0.0-beta.1 to 6.1.0-beta.1 matches. No ! or BREAKING 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.

Copy link
Copy Markdown
Contributor

@bokelley bokelley left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Release PR checks are green for 6.1.0-beta.1.

@bokelley bokelley merged commit 19fde5e into main May 23, 2026
23 checks passed
@bokelley bokelley deleted the release-please--branches--main branch May 23, 2026 21:27
@github-actions
Copy link
Copy Markdown
Contributor Author

🤖 Created releases:

🌻

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant