ci: use the same npmrc auth as metascraper - #26
Conversation
lerna/npm expand ${NPM_TOKEN} from the project .npmrc; pnpm 11
ignores that line. The release already set the token for pnpm, so
publish died with E404 on @microlink/google.
Co-authored-by: Cursor <cursoragent@cursor.com>
|
Warning Review limit reachedNext included review available in 26 minutes. View limit detailsLimit details: You’ve used the included review currently available. You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. Review configuration: ⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (2)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Coverage Report for CI Build 32820910782Warning Build has drifted: This PR's base is out of sync with its target branch, so coverage data may include unrelated changes. Warning No base build found for commit Coverage: 76.287%Details
Uncovered ChangesNo uncovered changes found. Coverage RegressionsRequires a base build to compare against. How to fix this → Coverage Stats
💛 - Coveralls |
2 participants
Summary
E404 PUT @microlink/google@1.2.0. That package already exists on npm (1.0.6) — this is missing npm auth, not a first-publish access problem.pnpm config setwas already in the workflow. lerna uses libnpmpublish/npm, which does not read that. Same recipe as metascraper / browserless / is-antibot: keep${NPM_TOKEN}in the project.npmrcfor npm, and ignorepnpm-lock.yaml.ci:merge skips the release job on purpose. Git is already ahead of npm (microlink.io@0.5.0,@microlink/mcp@2.1.0,@microlink/google@1.2.0tagged, not published). After this lands, those needlerna publish from-package(or the next real package change will leave them unpublished).Test plan
.npmrcis not rewritten with a raw token in CIlerna publish from-package --yesMade with Cursor