chore(main): release 7.0.0-rc.1 - #1014
Conversation
|
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. |
|
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. |
|
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. |
223f1a5 to
1023ff0
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. |
|
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. |
There was a problem hiding this comment.
Clean release-please cut for 7.0.0-rc.1. Release plumbing only — no source, no public surface touched. (Posting as comment: cannot self-approve, since I'm a co-author on this PR.)
Things I checked
- Diff is exactly 3 files:
.release-please-manifest.json(7.0.0-rc→7.0.0-rc.1),CHANGELOG.md(generated entry),pyproject.toml(7.0.0-rc→7.0.0rc1). Nosrc/changes. - Manifest/pyproject version split is intentional and correct: manifest keeps release-please semver (
7.0.0-rc.1); pyproject carries the PEP 440 normalized form (7.0.0rc1). The old7.0.0-rcstring was not valid PEP 440 — the normalization commit is the load-bearing fix here, not churn. - Migration note (
docs: note experimental TMPX migration, bokelley) accurately captures the breaking change from #1012:tmpx_macros/macros→tmpx_slots/chunks,IdentityMatchResponsereshaped to router-to-publisher, old-shape payloads no longer validate. Major bump is the right semver signal for that break; the breaking diff itself landed in #1012, this PR just cuts the RC. - No credential, auth, discriminated-union, or type-layering surface in the diff. Skip-everything list applies — no experts warranted.
Version normalizing itself as a separate bot commit is the kind of housekeeping that's easy to miss in a manifest-vs-pyproject drift; good that it's explicit here.
LGTM. Safe to merge.
bokelley
left a comment
There was a problem hiding this comment.
Reviewed the generated 7.0.0-rc.1 release diff: manifest and PEP 440 versions align, release entries match merged PRs, and the experimental Trusted Match/TMPX migration note is explicit. Approved for release once required checks pass.
4447ef6 to
3ef864e
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. |
|
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. |
There was a problem hiding this comment.
Standard release-please cut for 7.0.0-rc.1. Version bump plus generated changelog, no source touched — the release-automation happy path. Would approve; the API won't let me approve a PR this identity has a commit on, so this is a comment-verdict.
Things I checked
- Manifest and
pyproject.tomlcarry the two expected representations of the same version:.release-please-manifest.jsonholds semver7.0.0-rc.1,pyproject.tomlholds the PEP 440-normalized7.0.0rc1. That split is exactly what the "normalize prerelease version to PEP 440" commit and #1015 established —7.0.0-rc.1normalizes to7.0.0rc1. - No source under
src/adcp/changed. No public-API surface, no generated types, no discriminated-union machinery, no decisioning/auth paths. Skip-everything class — no experts warranted. - The TMPX migration note landed as prose in the changelog only. The actual breaking type change (
IdentityMatchResponsereshaped,tmpx_macros/macros->tmpx_slots/chunks) shipped in #1012, not here — this PR only documents it. Correctly captured with the "old-shape payloads no longer validate" callout for adopters. - Label is
autorelease: pending, not a human-hold label.
On merge this tag publishes to PyPI — the normalized 7.0.0rc1 is what lands there, so the earlier normalization fix is load-bearing for this cut to install cleanly.
LGTM.
|
🤖 Created releases: 🌻 |
|
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. |
🤖 I have created a release beep boop
7.0.0-rc.1 (2026-08-05)
Features
Migration Notes
tmpx_macros/macroswith publisher-ownedtmpx_slots/chunks.IdentityMatchResponsenow models the router-to-publisher response shape; its import alias remains available, but old-shape payloads no longer validate.Bug Fixes
This PR was generated with Release Please. See documentation.