Skip to content

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

Open
MGPOCKY wants to merge 1 commit into
BuilderIO:mainfrom
MGPOCKY:fix/ci-node-version-mismatch
Open

fix(ci): align workflow Node.js version with package engines#4756
MGPOCKY wants to merge 1 commit into
BuilderIO:mainfrom
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 22, 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 22 (using 22 where a concrete pin is needed).

  • .github/workflows/lint-and-commit.yml
    • node-version: '24.x'node-version: '22.x'
  • .github/workflows/publish-sdks.yml
    • node-version: '24.x'node-version: '22.x'
  • .github/workflows/react-native-sdk-test-remote.yml
    • node-version: '24.x'node-version: '22.x'

Test plan

  • Package engines.node / volta.node / .nvmrc is still 22
  • 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.


Note

Low Risk
Workflow-only Node version pins with no application or runtime logic changes.

Overview
Aligns three GitHub Actions workflows with the repo’s Node 22 target by changing setup-node from node-version: '24.x' to '22.x'.

Affected workflows: auto lint/commit (lint-and-commit.yml), SDK publish (publish-sdks.yml), and React Native remote E2E (react-native-sdk-test-remote.yml). This brings them in line with ci.yml and package engines / .nvmrc expectations so those jobs no longer run on Node 24.

Reviewed by Cursor Bugbot for commit 724dbd4. Bugbot is set up for automated code reviews on this repo. Configure here.

@changeset-bot

changeset-bot Bot commented Jul 31, 2026

Copy link
Copy Markdown

⚠️ No Changeset found

Latest commit: 724dbd4

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@MGPOCKY
MGPOCKY marked this pull request as ready for review July 31, 2026 08:54
@builder-io-integration

Copy link
Copy Markdown
Contributor

Review Agent skipped this PR — @MGPOCKY doesn't have a Builder seat in this space.

If you're @MGPOCKY: you may already have a seat under a different GitHub account. Reconnect GitHub

If you're an admin: Add @MGPOCKY to this space

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