chore: sync rc4 lockfile metadata#2127
Merged
Merged
Conversation
![aao-ipr-bot[bot]](https://avatars.githubusercontent.com/u/134922?s=60&v=4){kind=small}
There was a problem hiding this comment.
LGTM. Lockfile-only catch-up after the 8.1.0-beta.17 bump — three lines, zero behavior change.
Things I checked
- Diff is metadata-only: root
versionand CLI workspace@adcp/sdkdep range bumped from8.1.0-beta.16to8.1.0-beta.17(package-lock.json:3,9,7359). No package additions, removals, or integrity-hash churn. - No source touched — nothing under
src/lib/**,bin/**, orscripts/**, so the changeset rule doesn't fire. The version itself was bumped in the prior rc4 PR; this is the lockfile catching up. - All gates green, including
Check for changeset,Library Build,Typecheck & Build, andPack SDK runner.
Safe to merge.
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.
Updates package-lock metadata to match the rc4 package version already present in package.json. This keeps the root package and bundled CLI workspace dependency aligned at 8.1.0-beta.17. The root cause was a stale lockfile after the AdCP 3.1.0-rc.4 version bump. Validated with sync-version, schemas:ensure, build:lib, targeted schema/version tests, and the pre-push typecheck/build hook.