chore: update shared npm release workflow - #31
Conversation
|
You have reached your Codex usage limits for security reviews. Please try again later. |
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (1)
Included review availability: Your plan provides up to 1 included review per hour; 0 remain after this review. 📝 WalkthroughWalkthroughThe release job now references commit ChangesRelease workflow
Estimated code review effort: 1 (Trivial) | ~2 minutes Merge Risk: ⚪ Minimal · up to This localized workflow pin update preserves the existing release inputs and semantics while adopting the specified registry-visibility polling behavior; no actionable merge-blocking risk remains beyond normal checks and review. 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
Full details: Docstring CoverageExplanation No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0 files. (1 skipped: 1 unsupported.) ✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Update the shared npm release workflow pin to immutable commit dd6e8fa51339814159486cd92b5ae3a051eb15d2, which includes five-minute npm registry visibility polling before completing a release. Caller inputs and release semantics stay unchanged.
CC on behalf of jan-kubica
Summary by CodeRabbit