Repository navigation
v1.3.1: A hung npmscan API no longer fails your check
·
45 commits
to main
since this release
Immutable
release. Only release title and notes can be modified.
@v1 points to v1.4.0, which includes this fix.
Fixes
- If npmscan.com accepted a connection but never answered, the action could wait up to 16 minutes. A job with
timeout-minutes: 10was killed first and showed as a failed check, even withfail-on-error: false. The action now gives up within about 4.5 minutes per file and reports a warning, so an outage never blocks your merges.
Worth knowing
- Give the job at least 5 minutes per scanned file plus some slack (10 for one file).
- Thanks to @jsteinich for finding this in a review.
📖 Full docs: https://npmscan.com/docs/github-action