Migrate npm and git refs to Forgejo (RAIL-HO-WP-0006)
All checks were successful
CI Smoke / host-smoke (push) Successful in 1s
CI Smoke / container-smoke (push) Successful in 20s

This commit is contained in:
tegwick 2026-07-09 11:59:08 +02:00
parent 8c24e44857
commit 6de4d31bde
5 changed files with 10 additions and 10 deletions

View file

@ -28,7 +28,7 @@ tagged version; your lockfile becomes the real pin.
```bash
# .npmrc in your repo (see PUBLISHING.md for the read-token routing)
# @whynot:registry=https://gitea.coulomb.social/api/packages/coulomb/npm/
# @whynot:registry=https://forgejo.coulomb.social/api/packages/coulomb/npm/
npm i @whynot/design@0.3.0 lit
```

View file

@ -345,7 +345,7 @@ This staging is exactly the *"low-cost learning first"* posture in `whynot-contr
For whoever is bootstrapping this repo right now:
- [ ] Push the seed contents to `gitea.coulomb.social/coulomb/whynot-design`.
- [ ] Push the seed contents to `forgejo.coulomb.social/coulomb/whynot-design`.
- [ ] Cut the first real tag with `make release VERSION=x.y.z` (see §6 — *Release ritual*) so consumers can pin.
- [ ] Add the repo as a remote dependency in **one** consuming app (the Django one) and verify imports work end-to-end. Follow [`MultiFrameworkSupport.md` §Django](./MultiFrameworkSupport.md#django-server-rendered-templates--htmx).
- [ ] Open one trivial PR against `whynot-design` (e.g. a CHANGELOG typo) to confirm CI passes end-to-end.

View file

@ -5,7 +5,7 @@ repos can pin a version (`npm i @whynot/design@x.y.z`) and track it at their own
(WHYNOT-WP-0003). The git tag cut by `make release` (see `DesignSystemIntroduction.md`
§6) is the version; publishing makes that version installable.
- Registry: `https://gitea.coulomb.social/api/packages/coulomb/npm/`
- Registry: `https://forgejo.coulomb.social/api/packages/coulomb/npm/`
- `package.json` `publishConfig.registry` already points `npm publish` here.
- `lit` is a **peerDependency** — consumers install it themselves so their bundler
dedupes to a single `lit` instance.
@ -42,8 +42,8 @@ then install the package plus the `lit` peer:
```ini
# .npmrc
@whynot:registry=https://gitea.coulomb.social/api/packages/coulomb/npm/
//gitea.coulomb.social/api/packages/coulomb/npm/:_authToken=${NPM_AUTH_TOKEN}
@whynot:registry=https://forgejo.coulomb.social/api/packages/coulomb/npm/
//forgejo.coulomb.social/api/packages/coulomb/npm/:_authToken=${NPM_AUTH_TOKEN}
```
```sh

View file

@ -43,13 +43,13 @@ Install from the coulomb Gitea npm registry (add the scope to your `.npmrc` firs
```ini
# .npmrc
@whynot:registry=https://gitea.coulomb.social/api/packages/coulomb/npm/
//gitea.coulomb.social/api/packages/coulomb/npm/:_authToken=${NPM_AUTH_TOKEN}
@whynot:registry=https://forgejo.coulomb.social/api/packages/coulomb/npm/
//forgejo.coulomb.social/api/packages/coulomb/npm/:_authToken=${NPM_AUTH_TOKEN}
```
```sh
npm i @whynot/design@0.3.0 lit
# or pin straight from git: pnpm add git+ssh://git@gitea.coulomb.social/coulomb/whynot-design.git#v0.3.0
# or pin straight from git: pnpm add git+ssh://git@forgejo.coulomb.social/coulomb/whynot-design.git#v0.3.0
```
```js

View file

@ -65,10 +65,10 @@
"keywords": ["whynot", "design-system", "wireframe", "prototype", "lit", "web-components", "django", "react"],
"repository": {
"type": "git",
"url": "git+ssh://git@gitea.coulomb.social/coulomb/whynot-design.git"
"url": "git+ssh://git@forgejo.coulomb.social/coulomb/whynot-design.git"
},
"publishConfig": {
"registry": "https://gitea.coulomb.social/api/packages/coulomb/npm/"
"registry": "https://forgejo.coulomb.social/api/packages/coulomb/npm/"
},
"license": "UNLICENSED"
}