Skip to content

Conversation

@yogeshchoudhary147
Copy link
Contributor

@yogeshchoudhary147 yogeshchoudhary147 commented Jan 13, 2026

Fixes CI failures caused by Node version inconsistencies across workflows. npm 11 was already in use for trusted publishing - this PR centralizes the setup and standardizes Node versions throughout.

  • Created centralized setup-node-npm action for consistent configuration
  • Standardized Node version across all workflows
  • Regenerated package-lock.json with npm 11.7.0
  • Fixes npm ci failures from version mismatch

- Upgraded to npm 11.7.0 to match CI environment
- Regenerated package-lock.json to fix npm ci failures
- Resolves issue where npm 11 in CI couldn't use npm 10 lock file
@yogeshchoudhary147 yogeshchoudhary147 requested a review from a team as a code owner January 13, 2026 08:19
- Create reusable setup-node-npm action to standardize Node/npm setup
- Update all workflows and actions to use centralized setup
- Ensures npm 11.x is used consistently across all CI jobs
- Required for trusted publishing support (npm >= 11.5.1)
@yogeshchoudhary147 yogeshchoudhary147 changed the title fix: regenerate package-lock.json with npm 11 chore: upgrade to npm 11 for trusted publishing Jan 13, 2026
@yogeshchoudhary147 yogeshchoudhary147 changed the title chore: upgrade to npm 11 for trusted publishing chore: centralize Node/npm setup to fix CI failures Jan 13, 2026
@yogeshchoudhary147 yogeshchoudhary147 merged commit 0ec040d into main Jan 13, 2026
8 of 9 checks passed
@yogeshchoudhary147 yogeshchoudhary147 deleted the fix/npm-11-lock-file branch January 13, 2026 11:57
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