Skip to content

[release] fix(deps): pin @types/node to 24.3.2 so the official build can restore - #1499

Merged
Jayanth Reddy Bujula (jbujula) merged 1 commit into
release/stablefrom
users/jbujula/pin-types-node-24.3.2-release
Oct 7, 2026
Merged

Jayanth Reddy Bujula (jbujula) merged 1 commit into
release/stablefrom
users/jbujula/pin-types-node-24.3.2-release

Conversation

@jbujula

Copy link
Copy Markdown
Collaborator

Cherry-pick of #1498 for release/stable. package.json and package-lock.json are identical on main and release/stable, so the change is byte-for-byte the same.

BT-Official (ADO 21491) packages release/stable, and it currently fails restoring @types/node 24.3.3 from DPX-Tools-Upstream (build 22669950). This pins @types/node to 24.3.2, the only 24.3.x the feed can serve. See the main PR for details.

BT-Official (ADO 21491, build 22669950) fails in "NPM: Pre-install
cli-wrapper from DPX-Tools-Upstream":

  npm error 404 Not Found - GET .../DPX-Tools-Upstream/npm/registry/@types/node/-/node-24.3.3.tgz

@types/node also exists in internal upstreams of DPX-Tools-Upstream, so the
feed's default upstream behavior hides the npmjs versions and only serves the
copies those feeds already hold. 24.3.2 is the only 24.3.x it can serve.

Pin the override to exactly 24.3.2: same 24.3 line as before, dev-only type
definitions, one patch lower. A range like ~24.3.2 would resolve back to
24.3.3. Lockfile change is the single @types/node entry.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
@jbujula
Jayanth Reddy Bujula (jbujula) merged commit 416356d into release/stable Oct 7, 2026
3 checks passed
@jbujula
Jayanth Reddy Bujula (jbujula) deleted the users/jbujula/pin-types-node-24.3.2-release branch October 7, 2026 23:32
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