🎥 Make videos programmatically with React
Skills: Check npm release status before accepting delays
JonnyBurger5cffece67d04
diff --git a/.agents/skills/release/SKILL.md b/.agents/skills/release/SKILL.mdindex a088c40cce..255224a57d 100644--- a/.agents/skills/release/SKILL.md+++ b/.agents/skills/release/SKILL.md@@ -18,9 +18,15 @@ description: Release a new Remotion version- Run `bun set-version.ts <version>`, where <version> is the current version plus 1. If the exit code is not 0, abort the entire release process immediately.- Run `cd packages/example && sh runlambda.sh && cd ../..`. If this fails, abort the release.- Run `NPM_CONFIG_TOKEN=<token> bun run release` where <token> is the NPM token we just created- - An npm `409 Cannot publish over previously staged version "<version>"` is acceptable and does not block release completion when `npm stage list` and the `/-/stage` API show no staged version or stage ID to approve. Let the registry settle itself; do not keep retrying, waiting, or attempting manual fixes for this state. Continue the release workflow.- - Mention the affected package and version in the release summary as an accepted registry delay with availability pending. `bun publish --tolerate-republish` may report success despite this conflict, so do not claim that the affected version is already available on npm. This exception applies only to this staging conflict; other publish failures remain errors.-- Run `bun run publishtemplates` from the repository root to republish every template with the newly released packages. If any template fails to publish, stop the release workflow and report the failure.+ - Ordinary publishing already triggers [npm's automatic malware scan](https://github.blog/changelog/2026-07-28-npm-publish-time-malware-scanning-and-dual-use-metadata/); no separate staging step is needed for the current direct-publish workflow. Availability commonly takes around five minutes, sometimes 15 minutes or longer. These times are not guarantees.+ - Verify every public package selected by `publish.ts` with `npm view <package>@<version> version --json`. A successful `bun publish --tolerate-republish` exit is not proof of availability: it can hide a `409 Cannot publish over previously staged version "<version>"`.+ - For missing versions or staging conflicts, check the [npm lifecycle status API](https://api-docs.npmjs.com/): `GET https://registry.npmjs.org/-/package/<encoded-package-name>/version/<version>/status`, authenticated with a token that has publish access. URL-encode scoped names, for example `@remotion%2Fwhisper-web`. Keep credentials out of logs.+ - If the status is `validating`, poll status and exact-version availability once per minute for up to 15 minutes while continuing independent release work. Do not republish or restage the same version while scanning is pending. If it is still validating after this observation window, report it as an acceptable pending scan with its last observed status, not as available or guaranteed to become available.+ - If the version is awaiting maintainer approval, use `npm stage list <package> --json` and `npm stage view <stage-id> --json` to verify the package and version. [Wait for scanning to finish before approval](https://github.blog/changelog/2026-09-03-multiple-trusted-publishing-configurations-for-npm/), then run `npm stage approve <stage-id> --otp=<fresh-otp>` using the authenticated maintainer session and the 2FA instructions above. Waiting alone does not approve a staged version. Recheck exact-version availability after approval or a published status.+ - An empty stage list does not prove that scanning is pending or that a conflict will resolve itself. If the status API is unavailable, check `npm stage list` and the package's versions page on npmjs.com while logged in as a maintainer. A status API `403` can mean the endpoint is not enabled for this package; `404` can mean a missing version or insufficient access. Report blocked, rejected, manual-review, or unknown states and unresolved errors explicitly; do not classify them as acceptable scanning delays.+ - If npm explicitly returns `E_STAGE_REQUIRED`, follow [staged publishing](https://docs.npmjs.com/cli/v11/commands/npm-stage/): use `npm stage publish <tarball>` with the affected package's prepared release artifact, wait for scanning, then review and approve its stage as above. A staging 409 alone is not a reason to switch workflows or upload again.+ - In the release summary, distinguish verified available packages, confirmed pending scans, stages awaiting approval, and unresolved failures. Include the affected package and version for every pending or failed item. Other publish failures remain errors.+- Once the new package versions needed by the templates are available, run `bun run publishtemplates` from the repository root to republish every template. If a required version is still pending, report template publishing as pending too. If any template fails to publish, stop the release workflow and report the failure.- Generate a changelog in markdown and save it to `/tmp/release-<version>.md`:- Run `git log v<previous_version>..v<new_version> --oneline` to get all commits- Extract PR numbers from merge commits