Repository navigation
fix(deps): pin @types/node to 24.3.2 so the official build can restore - #1498
Merged
Jayanth Reddy Bujula (jbujula) merged 1 commit intoOct 7, 2026
Merged
Conversation
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>
Brad Flood (brflood)
approved these changes
Oct 7, 2026
Jayanth Reddy Bujula (jbujula)
deleted the
users/jbujula/pin-types-node-24.3.2
branch
October 7, 2026 23:32
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.
Why
The official build (ADO BT-Official, pipeline 21491, build 22669950) fails in NPM: Pre-install cli-wrapper from DPX-Tools-Upstream:
@types/nodealso exists in internal upstream feeds of DPX-Tools-Upstream. With the feed's default ("auto") upstream behavior, Azure Artifacts then hides the npmjs versions and serves only the copies those internal feeds already hold. 24.3.2 is the only 24.3.x it can serve. 24.3.3 restored fine on 2026-08-18 and 404s now.Change
package.json:overrides."@types/node"~24.3.0->24.3.2. It has to be an exact pin, because~24.3.2would resolve back to 24.3.3.package-lock.json: the single@types/nodeentry, 24.3.3 -> 24.3.2. Nothing else changes.Same 24.3 line as before, dev-only type definitions, one patch lower.
Validation
@types/node24.3.3 was the only one the feed can't serve.npm ci --dry-runpasses, and every@types/nodein the tree resolves to 24.3.2.buildchecks on this PR run the fullnpm ci+ build + tests.Notes
release/stable(what the official build packages) is in [release] fix(deps): pin @types/node to 24.3.2 so the official build can restore #1499.@types/node(andesbuild, which breaks the Actions compliance build the same way) on DPX-Tools-Upstream. Once that's done, this pin can go back to a range.