Migrate whynot-design npm catalog and docs to Forgejo registry
All checks were successful
CI Smoke / host-smoke (push) Successful in 1s
CI Smoke / container-smoke (push) Successful in 3s

Update catalog, docs, tests, and exec_delivery comment for Forgejo npm API.
This commit is contained in:
tegwick 2026-07-09 11:38:15 +02:00
parent ff0dc8aeb2
commit 0ab9c649b9
7 changed files with 10 additions and 10 deletions

View file

@ -13,7 +13,7 @@
A catalog entry carries `org` + `repo` explicitly (never a bare "owner"), and the
npm registry/scope live in `delivery_config.npm` as data — the engine never
hardcodes a registry. The pilot publishes `@whynot/design` from the
`coulomb/whynot-design` repo to `https://gitea.coulomb.social/api/packages/coulomb/npm/`.
`coulomb/whynot-design` repo to `https://forgejo.coulomb.social/api/packages/coulomb/npm/`.
## Install