Skip to content

Fix Publish Package workflow: bump Node to 24 for npm@latest compat#150

Merged
PavelLoparev merged 1 commit into
masterfrom
fix/publish-workflow-npm-node-compat
Jul 17, 2026
Merged

Fix Publish Package workflow: bump Node to 24 for npm@latest compat#150
PavelLoparev merged 1 commit into
masterfrom
fix/publish-workflow-npm-node-compat

Conversation

@PavelLoparev

Copy link
Copy Markdown
Contributor

Summary

  • The 2.35.1 tag push triggered Publish Package and it failed at the npm install -g npm@latest step: EBADENGINE, npm's latest major now requires Node ^22.22.2 || ^24.15.0 || >=26.0.0, but the workflow pinned Node 20.
  • npm ci/npm publish never ran, so nothing was actually published to the npm registry under 2.35.1.
  • Bumps node-version from 20 to 24 in .github/workflows/publish.yml to match.

Unrelated to AUT-1496's code changes (PR #149) - this is a CI infra fix surfaced when trying to publish that release.

Test plan

  • N/A - infra-only change; will be validated by the next tag push actually completing npm publish successfully

Co-Authored-By: Claude Sonnet 5 noreply@anthropic.com

npm's latest major release now requires Node ^22.22.2 || ^24.15.0 ||
>=26.0.0, but the workflow pinned Node 20 while its "Update npm" step
installs npm@latest unconditionally - EBADENGINE failure before npm ci
even runs. Bumps node-version to 24 to match.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
@PavelLoparev
PavelLoparev merged commit 87d798c into master Jul 17, 2026
@PavelLoparev
PavelLoparev deleted the fix/publish-workflow-npm-node-compat branch July 17, 2026 08:38
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.

1 participant