Skip to content

YC (S26) | Open Computer History | Continuously record your company computer work, map your workflows, help you find work worth automating, and power your agents' context

fix(ci): restore npm token fallback for CLI packages (#6912)

Ezra Ellette98a5ef0c3e38
diff --git a/.github/workflows/release-cli.yml b/.github/workflows/release-cli.yml
index f3947fd6f..8b8339731 100644
--- a/.github/workflows/release-cli.yml
+++ b/.github/workflows/release-cli.yml
@@ -986,6 +986,12 @@ jobs:
# every error — versions 0.3.290..0.3.295 all "succeeded" without ever
# publishing because the npm token had expired and nobody noticed.
- name: Publish platform packages
+ # npm prefers the job's OIDC identity when a package has trusted
+ # publishing configured, then falls back to this shared release token.
+ # Keep the fallback until every platform package has its own trusted
+ # publisher configuration on npm.
+ env:
+ NODE_AUTH_TOKEN: ${{ secrets.NPM_TOKEN }}
run: |
for pkg in screenpipe-darwin-arm64 screenpipe-darwin-x64 screenpipe-linux-x64 screenpipe-win32-x64; do
cd packages/cli/$pkg
@@ -1045,6 +1051,8 @@ jobs:
done
- name: Publish main package
+ env:
+ NODE_AUTH_TOKEN: ${{ secrets.NPM_TOKEN }}
run: |
cd packages/cli/screenpipe
err=$(mktemp)