Skip to content

Fix npm publish to use correct registry - #1614

Merged
asabaylus merged 1 commit into
mainfrom
claude/fix-npm-publish-auth-0ZEkD
Jan 17, 2026
Merged

Fix npm publish to use correct registry#1614
asabaylus merged 1 commit into
mainfrom
claude/fix-npm-publish-auth-0ZEkD

Conversation

@asabaylus

Copy link
Copy Markdown
Owner

Add publishConfig to package.json to explicitly specify npm registry.
This prevents npm from trying to publish to the yarn registry.

Fixes authentication error where npm was attempting to publish to
https://registry.yarnpkg.com instead of https://registry.npmjs.org

Add publishConfig to package.json to explicitly specify npm registry.
This prevents npm from trying to publish to the yarn registry.

Fixes authentication error where npm was attempting to publish to
https://registry.yarnpkg.com instead of https://registry.npmjs.org
@asabaylus
asabaylus merged commit 828aed6 into main Jan 17, 2026
7 checks passed
@asabaylus
asabaylus deleted the claude/fix-npm-publish-auth-0ZEkD branch January 17, 2026 14:02
@codecov

codecov Bot commented Jan 17, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 100.00%. Comparing base (ca9688e) to head (013df6f).
⚠️ Report is 1 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff            @@
##              main     #1614   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files            7         7           
  Lines          238       238           
  Branches        47        47           
=========================================
  Hits           238       238           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

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