chore: revert unpublished 6.0.0; next cut is 5.2.0 - #623
Merged
Conversation
npm 6.0.0 was published in error and has been unpublished. 5.x had no adopters, so we're treating it as beta and collapsing the work into a single minor bump instead of a major. - package.json back to 5.1.0 to match the current npm state - CHANGELOG.md 6.0.0 section removed - Rollup changeset (minor) captures all the accumulated work; next release PR will regenerate a clean 5.2.0 entry with breaking-change notices preserved as a heads-up Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Picks up an expanded docstring on ComplyTestControllerRequest ("Naturally
idempotent..." paragraph) added upstream. Comment-only, no functional
change.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
bokelley
force-pushed
the
bokelley/revert-6-to-5.2
branch
from
April 19, 2026 18:51
be773bc to
90ba62b
Compare
This was referenced Apr 19, 2026
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.
Summary
npm 6.0.0 was published in error (no 5.x adopters, should have been beta). Unpublished from npm via
npm unpublish @adcp/client@6.0.0— the 6.0.0 version slot is now permanently burned. This PR cleans up the repo to match.Changes
package.jsonback to5.1.0(current npm state). Next release PR will bump to 5.2.0 via the rollup changeset.CHANGELOG.md6.0.0 section stripped (1108 lines). The next release PR will regenerate a clean 5.2.0 entry from the changeset..changeset/rollup-5-2-0.md— single minor changeset that captures everything that was in the unpublished 6.0.0, with a prominent "Heads-up if tracking 5.1.0 → 5.2.0" section for the real API changes (verifier v3 return shape, governance status narrowing,budget.authority_levelremoval,domain → protocolrename).Follow-ups for whoever merges
git tag -d v6.0.0andgit push origin :refs/tags/v6.0.0gh release delete v6.0.0 --cleanup-tagWhy not cut 6.0.1 forward instead?
User call — nobody on 5.x yet, the functional changes are big but the API surface is additive enough that demoting the bump to minor is honest, and keeping the 5.x line tidy is preferable to an abandoned 6.0.0 on npm history.
🤖 Generated with Claude Code