Repository navigation
test(snapshots): use a recorded package in the install shortcut case - #3305
Merged
Merged
Conversation
The case installed tslib from the public registry, so pnpm started printing "(2.9.1 is available)" after tslib 2.9.1 was published on 2026-10-30. Install is-number 7.0.0 instead: the shared registry fixtures record it with a fixed latest tag, so the output no longer changes with upstream releases. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
🚀 Deploying Preview to Cloudflare 🚀Preview URL: https://claude-install-shortcut-recorded-package-viteplus-dev.voidzero-docs.workers.dev (commit ff184f9)This URL reflects your latest Preview deploymentPreview Deployments by commit
|
fengmk2
approved these changes
Nov 1, 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
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.
command_install_shortcutinstalledtslib@2.8.1from the public npm registry. pnpm prints a notice when a newer version exists, and tslib 2.9.1 came out on 2026-10-30 at 20:20 UTC. Since then the snapshot fails on every platform's shard 3/3, for example in this CI run (Linux, macOS, Windows):main's last green CI run predates that release, somainis affected too.The case now installs
is-number@7.0.0. The snapshot runner serves that package from its checked-in registry fixtures, where thelatesttag is fixed. Upstream releases can no longer change this output. The case only checks thatvp run installruns the install and skips resolution on the second run, so the choice of package doesn't matter otherwise.The npm and yarn cases that also install tslib don't print availability notices, so they are unchanged.
🤖 Generated with Claude Code