The libraries whose manifests name npm among their registries MUST be published by one workflow, release.auto.yml, made by the same model and run by hand from main (never by a push or a tag), that reads the release record (commons/generated/release.auto.json, commons libraries 0001-libraries FR-014), leaves out what is tagged, proves each library and packs it with the library's own tools/pack.ts, and, where the run is asked to publish, sends the tarballs in the order of the record (a library after the libraries it imports) to npm with provenance by npm's trusted publishing (the run's id-token), or with the repository's secret INFRO_NPMJS_TOKEN where the repository has it, and to the GitHub package registry with the workflow's own token, skips a version a registry has already, and makes the tag <name>-v<version> with the runner's token; the generator MUST find a library published to npm that has no tools/pack.ts, and MUST write no workflow of a library's own.
Enforced (check): .github: cd commons/libraries && bun test suite/ — workflows.test.ts: the one release workflow is run by hand from main, plans, proves and packs each library, publishes in the order of the record to npm with provenance (the token only where the repository has it) and to GitHub with its own token, skips a version that is there and tags with the runner; no library has a workflow of its own; a library with npm and no tools/pack.ts is a finding
Tests: passed: suite/workflows.test.ts the one release workflow is run by hand from main and publishes in the order of the plan:
Cited by: Libraries, Libraries by concern