Skip to content

Run GitHub actions through latest Node.js LTS by default (currently v24) (#2063)#2064

Open
robhogan wants to merge 1 commit into
static_hfrom
export-D109435888
Open

Run GitHub actions through latest Node.js LTS by default (currently v24) (#2063)#2064
robhogan wants to merge 1 commit into
static_hfrom
export-D109435888

Conversation

@robhogan

Copy link
Copy Markdown
Contributor

Summary:

As part of migrating npm publishing to Trusted Publish (OIDC), we'll need to use npm CLI at minimum 11.5.1, which is bundled with Node v24.

This bumps the setup-node action for both publishing branches to the alias lts/* from the fixed 22.14.0. Version ranges should be preferred over fixed versions to allow security fixes to be picked up in any case - this goes further than strictly necessary by moving to the dynamic lts/* alias (latest LTS). IMO that feels like a sensible, low-maintenance default.

Differential Revision: D109435888

…24) (#2063)

Summary:

As part of migrating npm publishing to [Trusted Publish (OIDC)](https://docs.npmjs.com/trusted-publishers/), we'll need to use `npm` CLI at minimum 11.5.1, which is bundled with Node v24.

This bumps the `setup-node` action for both publishing branches to the alias `lts/*` from the fixed `22.14.0`. Version ranges should be preferred over fixed versions to allow security fixes to be picked up in any case - this goes further than strictly necessary by moving to the dynamic `lts/*` alias (latest LTS). IMO that feels like a sensible, low-maintenance default.

Differential Revision: D109435888
@meta-cla meta-cla Bot added the CLA Signed Do not delete this pull request or issue due to inactivity. label Jun 23, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

CLA Signed Do not delete this pull request or issue due to inactivity.

1 participant