Repository navigation
Conversation
Run #12 of the deploy workflow failed with a 503 from the npm audit endpoint. Nothing was wrong with the tree: npm could not reach the service, and `npm audit` exits non-zero for that exactly as loudly as it does for a real advisory. The commit was therefore never published, so the site kept serving the previous revision while the repo had moved on. Both workflows now call one script that reads the JSON report rather than the exit code. A transport error becomes a warning after three attempts, an unparsable report becomes a warning, and a critical advisory still fails the build. The critical threshold and the reason for it now live in one place instead of a comment duplicated in each workflow. Claude-Session: https://claude.ai/code/session_01XBecXxjFsZoeLPFsaebhwS
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This branch was successfully 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
1 participant
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.
Deploy run #12 failed on
Verify frontendwith a 503 fromregistry.npmjs.org/-/npm/v1/security/audits/quick. No advisory was found; npm could not be asked.npm auditexits 1 for both cases, so a registry blip gated the deploy and the "Name Unichain as the partner" commit never reached Pages. CI passed on the same commit, which is the tell: the tree was fine..github/scripts/npm-audit-gate.shnow reads the JSON report instead of trusting the exit code:{"error": ...}from the registry: retry up to three times 15s apart, then::warning::and pass::warning::and passmetadata.vulnerabilities.critical > 0:::error::and failBoth workflows call it, so the critical threshold and the reason behind it live in one place rather than in a comment duplicated in each file. The script is added to the deploy path filter so a change to the gate rebuilds the site it gates.
Verified against the real lockfile:
npm audit advisories -> critical: 0, high: 0, moderate: 0, low: 0, info: 0, exit 0. The report-parsing branches were exercised separately with mocked reports for the 503, string-error, clean, moderate/high-only, critical, and garbage cases.Merging this re-triggers the deploy, which is what gets the site back in sync with main.
https://claude.ai/code/session_01XBecXxjFsZoeLPFsaebhwS