chore: sync beta 18 lockfile metadata#2130
Merged
Merged
Conversation
There was a problem hiding this comment.
LGTM. Lockfile metadata catching up to the 8.1.0-beta.18 release commit (fd470d2) — exactly the fix package-lock.json drift wants.
Things I checked
- Diff is three lines: root
version, rootpackages[""].version, and the workspace dependency pin on@adcp/sdk— all moving8.1.0-beta.17→8.1.0-beta.18in lockstep - No source code touched, so changeset omission is correct (this is post-release bookkeeping, not published behavior)
lockfileVersion: 3unchanged, no dependency tree edits — pure metadata sync
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
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
Syncs
package-lock.jsonmetadata to the published8.1.0-beta.18package version.Validation
Pre-push validation passed, including TypeScript typecheck and library build.