Skip to content

fix(ci): align workflow Node.js version with package engines - #3013

Open
MGPOCKY wants to merge 1 commit into
codex-team:nextfrom
MGPOCKY:fix/ci-node-version-mismatch
Open

fix(ci): align workflow Node.js version with package engines#3013
MGPOCKY wants to merge 1 commit into
codex-team:nextfrom
MGPOCKY:fix/ci-node-version-mismatch

Conversation

@MGPOCKY

@MGPOCKY MGPOCKY commented Jul 31, 2026

Copy link
Copy Markdown

Why

Package metadata declares engines.node / volta.node / .nvmrc as 18, but CI workflows still pin node-version to a mismatched value.

That can make CI run on a runtime the project no longer supports (or skip the version the package actually targets).

What changed

Update the affected workflow node-version pins so they satisfy 18 (using 18 where a concrete pin is needed).

  • .github/workflows/bump-version-on-merge-next.yml
    • node-version: 16node-version: 18
  • .github/workflows/create-a-release-draft.yml
    • node-version: 16node-version: 18
    • node-version: 16node-version: 18
  • .github/workflows/publish-package-to-npm.yml
    • node-version: 16node-version: 18

Test plan

  • Package engines.node / volta.node / .nvmrc is still 18
  • Updated workflows now use versions consistent with that constraint
  • Relevant CI jobs on this branch look healthy

Found while auditing CI/package version consistency across popular repos.

@MGPOCKY
MGPOCKY marked this pull request as ready for review July 31, 2026 09:09
@neSpecc
neSpecc requested a review from Copilot August 3, 2026 13:51

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Updates GitHub Actions workflows to run CI/publish/release tasks on Node.js 18, aligning workflow runtime with the repository’s Node 18 toolchain expectations.

Changes:

  • Bump node-version from 16 → 18 in the npm publish workflow.
  • Bump node-version from 16 → 18 in the release-draft workflow (two jobs).
  • Bump node-version from 16 → 18 in the bump-version-on-merge workflow.

Reviewed changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated 3 comments.

File Description
.github/workflows/publish-package-to-npm.yml Updates publish job Node.js version pin to 18.
.github/workflows/create-a-release-draft.yml Updates Node.js version pins to 18 in release-draft related jobs.
.github/workflows/bump-version-on-merge-next.yml Updates Node.js version pin to 18 for automated version bumping.
Suppressed comments (1)

.github/workflows/publish-package-to-npm.yml:25

  • PR description claims package.json declares engines.node / volta.node as 18, but this repo’s package.json currently has neither engines nor volta fields (only .nvmrc pins Node to v18.20.1). Please either update the PR description or add the missing metadata if aligning CI to engines/volta is part of the intended change.
          node-version: 18

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Comment on lines 22 to 26
# Setup node environment
- uses: actions/setup-node@v1
with:
node-version: 16
node-version: 18
registry-url: https://registry.npmjs.org/
Comment on lines 70 to +73
# Setup node environment
- uses: actions/setup-node@v1
with:
node-version: 16
node-version: 18
Comment on lines 64 to +67
# Setup node environment
- uses: actions/setup-node@v1
with:
node-version: 16
node-version: 18
@neSpecc

neSpecc commented Aug 3, 2026

Copy link
Copy Markdown
Member

@MGPOCKY hey. Thanks for the PR, please, check comments above.

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.

3 participants