潮规有界,预览留标 · Honor npm tag invariants - #40
Merged
Merged
Conversation
Leave registry-required latest tags on first-published Tiny and Medium package names instead of attempting an unsupported deletion. Keep stable promotion scoped to the Small facade, shared runtime, and six native packages; preview maturity remains explicit in package metadata and CLI output.
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.
原因
公共 npm registry 的 package document 要求至少保留
latest;首次发布的新 package name 即使使用--tag next也会生成latest,删除它返回 HTTP 400。第一次 promotion run 因此在任何稳定 tag 变更前安全失败。变更
latest验证
python3 -m unittest tests.python.test_npm_release(12 tests)python3 -m unittest discover -s tests/python -p "test_*.py"(77 tests)git diff --check参考
latest。