Chris Tate 68e148add9 Wait for every released package to resolve on npm before the GitHub release ...

The release workflow publishes each package and moves on once npm accepts
the upload. A package whose processing on npm stalls was visible only on
npmjs.com.

A new npm-available job runs after "Publish to npm". It checks each package
of the release with `npm view <name>@<version> version --prefer-online`
every 2 minutes (scripts/wait-npm-available.mjs) until every package
resolves, and reports each package's time from upload to available in the
log and the job summary. When a package still does not resolve after 2
hours, the job fails and names each missing package and version. It only
reads from the registry.

The publish job lists every package of the release and records the time
npm accepted each upload, keeps those times with its upload receipts, and
passes both to the new job. Create GitHub Release now waits for the new
job, so the release is created and marked complete only once every
package resolves; a later release run checks again and skips uploads npm
already accepted.

2026-10-25 18:51:56 -05:00

..

ci.yml

Build the sanitized three.js nodes fixture in its own CI job

2026-10-25 06:49:46 -05:00

prune-caches.yml

List caches and open pull requests in full before pruning

2026-10-24 15:27:31 -05:00

release.yml

Wait for every released package to resolve on npm before the GitHub release

2026-10-25 18:51:56 -05:00