fix(ci): point package-lock resolved URLs at the official registry - #135
Merged
Conversation
The lockfile regenerated in 45b0958 recorded bnpm.byted.org resolved URLs, which neither GitHub runners nor the UAT build host can resolve. Same artifacts, same integrity hashes — only the mirror host changes.
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.
45b0958 重生成 lockfile 时 resolved URL 记录了内网镜像 bnpm.byted.org（7 处），GitHub runner 与 UAT 构建主机均无法解析，npm ci 直接 ENOTFOUND。本 PR 仅把 resolved host 换回 registry.npmjs.org——包与 integrity 哈希完全不变。本地
npm ci --dry-run验证通过。