Skip to content

ci: remove committed npm auth config#141

Merged
francoischalifour merged 1 commit into
altertable-ai:mainfrom
albert20260301:fix/remove-npmrc-release-auth
Jun 30, 2026
Merged

ci: remove committed npm auth config#141
francoischalifour merged 1 commit into
altertable-ai:mainfrom
albert20260301:fix/remove-npmrc-release-auth

Conversation

@albert20260301

Copy link
Copy Markdown
Contributor

Summary

  • remove the committed .npmrc that forces local npm commands to use ${NPM_TOKEN}
  • revert release publishing back to bun publish
  • pass the CI npm token through Bun's supported NPM_CONFIG_TOKEN env var instead of NODE_AUTH_TOKEN/setup-node

Impact

Local npm commands no longer fail with E401 when NPM_TOKEN is unset. Release publishing still receives the npm automation token in CI without committing registry auth config.

Verification

  • bun install --frozen-lockfile
  • bun run build
  • NPM_CONFIG_TOKEN=dummy bun publish --dry-run --access public (packages/altertable-js)
  • NPM_CONFIG_TOKEN=dummy bun publish --dry-run --access public (packages/altertable-react)
  • git diff --check

@albert20260301

Copy link
Copy Markdown
Contributor Author

@francoischalifour this removes the repo-level .npmrc that was breaking local npm auth when NPM_TOKEN is unset, and keeps Bun publishing in CI using NPM_CONFIG_TOKEN per Bun's publish auth support. Can you review when CI finishes?

@francoischalifour francoischalifour merged commit 62b4297 into altertable-ai:main Jun 30, 2026
3 checks passed
@albert20260301 albert20260301 deleted the fix/remove-npmrc-release-auth branch June 30, 2026 14:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants