fix: pin commander tarball URL in bun.lock so CI install succeeds#25
Merged
MagicCube merged 1 commit intoMagicCube:mainfrom Apr 11, 2026
Merged
Conversation
The commander entry was the only lockfile entry pointing at registry.npm.taobao.org, whose TLS cert is expired and causes `bun install --frozen-lockfile` to fail on CI with `CERT_HAS_EXPIRED downloading tarball commander@14.0.3`. Repoint it to registry.npmmirror.com to match the other 259 entries in the lockfile. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
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
2 participants
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
The
commanderentry inbun.lockis the only entry pointing atregistry.npm.taobao.org, whose TLS cert is currently expired. This causesbun install --frozen-lockfileto fail on GitHub Actions with:Every other entry in the lockfile (259 of them) already points to
registry.npmmirror.com, which works fine. This PR repoints commander to the same host so the lockfile is internally consistent and CI can install dependencies again.