peezy-tech/codex-flows
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Document npm publishing prerequisites

Browse source
This commit is contained in:
matamune 2026-05-12 15:17:34 +00:00
parent 3c446b11a4
commit 46878f0e15
3 changed files with 7 additions and 2 deletions
Download patch file Download diff file Expand all files Collapse all files

3
.github/workflows/publish-codex-flows.yml vendored
View file

@ -32,6 +32,9 @@ jobs:
node-version: 24
registry-url: https://registry.npmjs.org
- name: Update npm
run: npm install -g npm@^11.10.0
- name: Install dependencies
run: bun install --frozen-lockfile

4
README.md
View file

@ -76,7 +76,9 @@ bun run --filter @peezy-tech/codex-flows release:check
```
Because the npm package does not exist yet, bootstrap the first version with a
human npm session or short-lived npm token from the public repo checkout:
human npm session or short-lived npm token from the public repo checkout. The
`peezy-tech` npm organization/scope must exist first, and the publishing account
or token must have write access to that scope:
```bash
cd packages/codex-client

2
packages/codex-client/README.md
View file

@ -110,7 +110,7 @@ bun run --filter @peezy-tech/codex-flows release:check
The release check runs package tests, type checking, a clean `dist` build, and `npm pack --dry-run`. Review the pack output before publishing so only `dist`, `README.md`, and package metadata are included.
For the first publish, use a human npm session or short-lived npm token from the public `peezy-tech/codex-flows` repo checkout:
For the first publish, use a human npm session or short-lived npm token from the public `peezy-tech/codex-flows` repo checkout. The `peezy-tech` npm organization/scope must exist first, and the publishing account or token must have write access to that scope:
```bash
cd packages/codex-client