ci: use npm pack --dry-run for publishable packages#427
Conversation
`npm publish --dry-run` still hits the registry and fails when the current version already exists. Switching to `npm pack --dry-run` validates packaging without the registry check, so the PR job no longer blocks on already-published versions. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
✅ Deploy Preview for graypaper-reader ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
|
Important Review skippedReview was skipped due to path filters ⛔ Files ignored due to path filters (5)
CodeRabbit blocks several paths by default. You can override this behavior by explicitly including those paths in the path filters. For example, including ⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
📝 WalkthroughWalkthroughThe CI workflow for Node.js changes the package validation step from running ChangesCI Workflow Dry-run Package Step
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~2 minutes Possibly related PRs
Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
Visual Regression Test Report ✅ PassedGithub run id: 25641466988 🔗 Artifacts: Download |
Summary
npm publish --dry-runstill hits the npm registry and refuses if the current version already exists, so the PR-time check kept failing onlinks-metadata@1.4.0(see run 24570858567).npm pack --dry-run, which validates packaging (file list, prepack hooks, tarball) without contacting the registry. The realpublish.ymljob is unchanged and still enforces version uniqueness at release time.Test plan
🤖 Generated with Claude Code
Summary by CodeRabbit