You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Mar 26, 2026. It is now read-only.
The jlpm steps in the CI workflow are currently using GITHUB_TOKEN for authentication, but jlpm/Yarn/NPM expects NODE_AUTH_TOKEN (or YARN_NPM_AUTH_TOKEN) for registry authentication.
Problem
When packages require GitHub Packages/NPM authentication, the install and audit steps will fail because GITHUB_TOKEN is not recognized by the npm registry authentication system.
Solution
Replace GITHUB_TOKEN with NODE_AUTH_TOKEN in the environment variables for the jlpm steps in .github/workflows/ci.yml:
Lines to fix:
Lines 52-59 (audit-prod job, jlpm install and audit steps)
Lines 76-83 (audit-all job, jlpm install and audit steps)
Issue
The jlpm steps in the CI workflow are currently using
GITHUB_TOKENfor authentication, but jlpm/Yarn/NPM expectsNODE_AUTH_TOKEN(orYARN_NPM_AUTH_TOKEN) for registry authentication.Problem
When packages require GitHub Packages/NPM authentication, the install and audit steps will fail because
GITHUB_TOKENis not recognized by the npm registry authentication system.Solution
Replace
GITHUB_TOKENwithNODE_AUTH_TOKENin the environment variables for the jlpm steps in.github/workflows/ci.yml:Lines to fix:
Change:
To:
Context