Repository navigation
Fix npm 12 release verification and prepare Shield 2.1.1 - #3
Merged
Merged
Conversation
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.
The 2.1.0 npm publication stopped before upload because npm 12 changed the JSON shape returned by
pack. Accept both the older array and the new package-keyed object, assert the packed name and version, and prevent inheritednpm publish --dry-runsettings from suppressing the test tarball and isolated installs.Prepare 2.1.1 without rewriting the existing release tag, and run package CI in the same Node/npm environment as publishing. Add a cleanly applying, formatted, type-checked patch against Vercel's current registry and a submission description. No upstream Vercel issue or PR is created.
Validation: the full
npm@12.2.0 publish --dry-run --access publiclifecycle passes, including 1,263 tests (two optional model tests skipped), build, and isolated AI SDK 5–7 runtime/types/example checks. Older npm package checks and both JSON formats also pass in the application checkout.