Bump Node to 24.17.0 to match consuming extensions#75
Merged
Conversation
|
🔒 Automated review in progress — @rchiodo is auto-reviewing this PR. |
edvilme
added
the
debt
Bump the patch version across VERSION, package.json, pyproject.toml, and package-lock.json alongside the Node toolchain update in this PR. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
rchiodo
reviewed
Jul 2, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Bumps the pinned Node version in .nvmrc from 22.21.1 to 24.17.0 to align the shared package's Node toolchain with the extensions that consume it.
Why
All five VS Code Python tool extensions (black-formatter, flake8, isort, mypy, pylint) currently pin 24.17.0 in their .nvmrc. When an extension integrates this package as a git submodule, it builds this package's TypeScript during npm install using the extension's Node version. Keeping this repo on 22.21.1 means the shared package is developed/tested under an older Node than it is actually built with downstream.
A new consistency check in the extensions' shared-package-submodule-sync workflow fails a sync if the extension's .nvmrc is older than this package's .nvmrc. Bumping here keeps the two in lockstep and avoids drift.
Change