Skip to content

Use Node 24 in the publish pipeline - #999

Merged
Anthony Kim (anthonykim1) merged 1 commit into
mainfrom
anthonykim1/use-node-24-publish
Oct 22, 2026
Merged

Anthony Kim (anthonykim1) merged 1 commit into
mainfrom
anthonykim1/use-node-24-publish

Conversation

@anthonykim1

Copy link
Copy Markdown
Contributor

Depends on: https://github.com/microsoft/vscode-engineering/pull/4306
Follow-up to: #997

  • Select Node.js 24.18.0 for the package and API-scan jobs through the shared npm-package nodeVersion input.
  • Run the Linux compile/test job on Node.js 24.18.0 instead of the shared Node 22 default.
  • Align publishing with GitHub Actions, native prebuilds, and the repository's strict Node 24 devEngines requirement.
  • Keep the shared template reference on main and leave the existing publish flags and release approval behavior unchanged.
  • Keep this draft blocked on the shared template change; until that merges, package and API scan still use Node 22.
  • Validate publish.yml with git diff --check and Ruby YAML parsing.

Inspirations from:

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
@anthonykim1
Anthony Kim (anthonykim1) marked this pull request as ready for review October 22, 2026 16:42
@anthonykim1
Anthony Kim (anthonykim1) merged commit 3b42f23 into main Oct 22, 2026
9 checks passed
@anthonykim1
Anthony Kim (anthonykim1) deleted the anthonykim1/use-node-24-publish branch October 22, 2026 16:43
@anthonykim1 Anthony Kim (anthonykim1) added this to the 1.144.0 milestone Oct 22, 2026
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.

2 participants