Skip to content

fix(ci): use compatible Node version for npm publish#103

Merged
dialupdisaster merged 1 commit into
mainfrom
fix/release-npm-node-version
Jul 16, 2026
Merged

fix(ci): use compatible Node version for npm publish#103
dialupdisaster merged 1 commit into
mainfrom
fix/release-npm-node-version

Conversation

@dialupdisaster

Copy link
Copy Markdown
Contributor

Summary

  • run the npm publishing job on the current Node 24 line
  • keep npm@latest compatible for provenance publishing
  • include formatting updates produced by the repository pre-commit hooks

Verification

  • pre-commit run --all-files
  • bun run typecheck
  • bun test (302 passed)

@github-actions

Copy link
Copy Markdown
Contributor

Found one issue:

  • P1 – Alternate publishing workflow remains broken. .github/workflows/release-please.yml:36 updates Node only for Release Please, while the tag/manual publishing path still uses incompatible Node 22.14 at .github/workflows/release.yml:23 and also installs npm@latest. Tag-triggered or manually dispatched releases can therefore still fail before publishing. Update both publishing workflows together.

@dialupdisaster
dialupdisaster merged commit 11591c5 into main Jul 16, 2026
7 checks passed
@dialupdisaster
dialupdisaster deleted the fix/release-npm-node-version branch July 16, 2026 02:37
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