Repository navigation
fix: avoid false failures after npm tag deletion - #257
Open
XXPermanentXX wants to merge 1 commit into
Open
XXPermanentXX wants to merge 1 commit into
XXPermanentXX wants to merge 1 commit into
Conversation
This branch has not been deployed
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 dist-tag rm成功后,registry 的紧接着一次查询可能仍返回旧标签。本次首次试跑已成功删除bailian-cli / release-test,但后置核验将旧数据误报为删除失败。删除后最多查询 5 次,查询间隔为 1、2、4、8 秒。只重试读取,删除命令只执行一次;标签持续存在或查询失败仍报错。补充旧数据最终收敛和重试上限的回归测试,并记录 npm 页面已确认清理连接为 Valid、无需发布版本。
验证
vp check:0 错误,3 个已有 warning。本 PR 没有执行其他线上标签删除,也没有发布 npm 版本。