Skip to content

fix(release): add verify-only npm recovery - #45

Merged
777genius merged 1 commit into
mainfrom
fix/npm-verify-only-recovery
Aug 8, 2026
Merged

fix(release): add verify-only npm recovery#45
777genius merged 1 commit into
mainfrom
fix/npm-verify-only-recovery

Conversation

@777genius

Copy link
Copy Markdown
Owner

Make post-publication verification genuinely retryable after workflow fixes.

The existing split publish/verify jobs prevent duplicate publication during a normal failed-job retry, but GitHub re-runs the original workflow SHA. If verifier code itself needs a fix, there was no safe way to run the corrected verifier against an immutable published version.

This adds a verify_only workflow input. In that mode:

  • the protected publish job is skipped
  • the publish-ready gate stays false
  • no OIDC publish permission or npm environment is used
  • package identity is resolved from the immutable release tag
  • the public signature, SLSA provenance, and isolated add/info/doctor/update/remove lifecycle still run

The maintainer runbook and fail-closed contract test cover the recovery path.

@777genius
777genius merged commit 80fe57a into main Aug 8, 2026
12 of 13 checks passed
@coderabbitai

coderabbitai Bot commented Aug 8, 2026

Copy link
Copy Markdown

Warning

Review limit reached

@777genius, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 47 minutes

You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository.

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 3b178d4b-d127-4304-8fac-725ab9fde57d

📥 Commits

Reviewing files that changed from the base of the PR and between b4bd54a and 704eaf5.

📒 Files selected for processing (3)
  • .github/workflows/agentplugins-npm-publish.yml
  • docs/agentplugins-release.md
  • repotests/agentplugins_release_contract_test.go

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.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@777genius
777genius deleted the fix/npm-verify-only-recovery branch August 8, 2026 20:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant