coulomb/whynot-design
4
0
Fork 0
Code Issues Pull requests Projects Releases Packages 1 Wiki Activity Actions

release: @whynot/design v0.4.2 on Forgejo

Browse source 
Assistant: codex
Assistant-Model: gpt-5.6-sol
Assistant-Session: 01a06d83-1cbc-71f2-b0dc-e0f48cedae43
This commit is contained in:
tegwick 2026-09-04 23:26:28 +02:00
parent 77cf04eb5e
commit 65247c9320
13 changed files with 88 additions and 23 deletions
Download patch file Download diff file Expand all files Collapse all files

11
PUBLISHING.md
View file

@ -1,6 +1,6 @@
# Publishing `@whynot/design`
`@whynot/design` is published to the **coulomb Gitea npm registry** so consuming
`@whynot/design` is published to the **coulomb Forgejo npm registry** so consuming
repos can pin a version (`npm i @whynot/design@x.y.z`) and track it at their own pace
(WHYNOT-WP-0003). The git tag cut by `make release` (see `DesignSystemIntroduction.md`
§6) is the version; publishing makes that version installable.
@ -12,13 +12,14 @@ repos can pin a version (`npm i @whynot/design@x.y.z`) and track it at their own
## The token (never commit it)
Publishing and installing `@whynot/*` need a Gitea package token. It is **not stored in
Publishing and installing `@whynot/*` need a Forgejo package token. It is **not stored in
this repo** — per `.claude/rules/credential-routing.md`, tokens are routed, not vended:
a Gitea package token is operator/OpenBao-owned (`railiance-platform`). Obtain one from
the operator and export it:
a Forgejo package token is operator/OpenBao-owned (`railiance-platform`). Use the
`whynot-design-npm-publish` governed lane for publishing; interactive operators may
export a value obtained through the same route:
```sh
export NPM_AUTH_TOKEN=… # Gitea package token; never paste into git/chat/logs
export NPM_AUTH_TOKEN=… # Forgejo package token; never paste into git/chat/logs
```
`.npmrc` (committed) references it via `${NPM_AUTH_TOKEN}` — no secret lives in the file.