From 2c75c8a1ec4e28adcbe569cdf161bd06d81c8dce Mon Sep 17 00:00:00 2001 From: dotta Date: Mon, 30 Mar 2026 12:44:26 -0500 Subject: [PATCH] docs: clarify npm prerequisites for first ui publish Co-Authored-By: Paperclip --- doc/PUBLISHING.md | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/doc/PUBLISHING.md b/doc/PUBLISHING.md index a3dd02c7a3..83a6c4a7be 100644 --- a/doc/PUBLISHING.md +++ b/doc/PUBLISHING.md @@ -108,6 +108,13 @@ Notes: - `prepack` automatically rewrites `ui/package.json` to the lean publish manifest, and `postpack` restores the dev manifest after the command finishes. - If `npm view @paperclipai/ui version` already returns the same version that is in [`ui/package.json`](../ui/package.json), do not republish. Bump the version or use the normal repo-wide release flow in [`scripts/release.sh`](../scripts/release.sh). +If the first real publish returns npm `E404`, check npm-side prerequisites before retrying: + +- `npm whoami` must succeed first. An expired or missing npm login will block the publish. +- For an organization-scoped package like `@paperclipai/ui`, the `paperclipai` npm organization must exist and the publisher must be a member with permission to publish to that scope. +- The initial publish must include `--access public` for a public scoped package. +- npm also requires either account 2FA for publishing or a granular token that is allowed to bypass 2FA. + ## Version formats Paperclip uses calendar versions: