whynot-design/workplans/WHYNOT-WP-0004-forgejo-npm-migration.md
tegwick 65247c9320 release: @whynot/design v0.4.2 on Forgejo
Assistant: codex
Assistant-Model: gpt-5.6-sol
Assistant-Session: 01a06d83-1cbc-71f2-b0dc-e0f48cedae43
2026-09-04 23:26:28 +02:00

55 lines
1.5 KiB
Markdown

---
id: WHYNOT-WP-0004
type: workplan
title: "Move @whynot/design publication to Forgejo Packages"
domain: infotech
repo: whynot-design
status: active
owner: codex
topic_slug: forgejo-npm-migration
created: "2026-09-04"
updated: "2026-09-04"
---
## Reconcile the package release state
```task
id: WHYNOT-WP-0004-T01
status: done
priority: high
```
Audit the partially completed Forgejo migration, choose a new immutable package
version when the existing Gitea release cannot be reused safely, and verify the
release contents before any credentialed write. This work promotes routed intake
`01a06e08-6936-7762-a347-f832182b7705`.
## Publish and verify the Forgejo package
```task
id: WHYNOT-WP-0004-T02
status: progress
priority: high
```
Use the governed `whynot-design-npm-publish` credential lane to publish the new
version to `https://forgejo.coulomb.social/api/packages/coulomb/npm/`. Verify an
authenticated exact-version install and the shipped IR/version contract without
printing or persisting the credential.
## Align consumer and operator documentation
```task
id: WHYNOT-WP-0004-T03
status: done
priority: medium
```
Make Forgejo the single canonical npm endpoint in current package, consumer, and
release guidance. Hand the verified endpoint to ops-warden for catalog and
playbook reconciliation.
Prepared `@whynot/design@0.4.2` on 2026-09-04. The package dry-run contains 105
files with IR `designVersion` 0.4.2; all five Playwright visual tests pass. The
changelog gate correctly reports no *post-release* `[Unreleased]` entry after the
0.4.2 section was cut.