fix(release): tolerate npm dist-tag propagation lag - #95
Conversation
|
Important Review skippedDraft detected. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## beta #95 +/- ##
=======================================
Coverage 90.16% 90.16%
=======================================
Files 38 38
Lines 3181 3181
Branches 948 944 -4
=======================================
Hits 2868 2868
Misses 290 290
Partials 23 23
Flags with carried forward coverage won't be shown. Click here to find out more. 🚀 New features to boost your workflow:
|
Summary
Why
The beta.9 packages published successfully, but the immediate npm view reads returned stale dist-tags. The wrapper treated that temporary registry propagation lag as a release failure and printed OTP repair commands even though no repair was ultimately needed.
Verification
No changeset is included because this changes repository release tooling only; beta.9 package contents and published tags remain unchanged.