Skip to content

[browser] Validate npm 11.19.1 through Node and VMR packages - #133394

Draft
kotlarmilos wants to merge 1 commit into
mainfrom
users/mkotlar/npm-11.19.1-wasm-validation
Draft

[browser] Validate npm 11.19.1 through Node and VMR packages#133394
kotlarmilos wants to merge 1 commit into
mainfrom
users/mkotlar/npm-11.19.1-wasm-validation

Conversation

@kotlarmilos

Copy link
Copy Markdown
Member

Description

This validates the npm 11.19.1 update in dotnet/node#396 through the standard runtime WASM PR pipelines. It updates all eight Node transports to 11.0.0-alpha.1.26457.5 from BAR 330858 and consumes Emscripten packages from VMR BAR 330868 through General Testing. The validation-only manifest-band override selects the published .NET 12-branded workload packages while retaining the existing .NET 11 SDK host and leaving global.json unchanged.

The official Node build succeeds at https://dev.azure.com/dnceng/internal/_build/results?buildId=3068942 and the official VMR build succeeds at https://dev.azure.com/dnceng/internal/_build/results?buildId=3069115. Publication at https://dev.azure.com/dnceng/internal/_build/results?buildId=3069257 completes package and blob publication but fails while downloading an SDK PDB. All required Emscripten packs and workload manifests are available in the testing feed. BAR 330868 is assigned to General Testing without repeating artifact publication.

This draft is for CI validation only and must not merge while it references General Testing.

Contributes to dotnet/node#396

Note

This pull request description and its changes were generated with GitHub Copilot.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Copilot-Session: cf4fdbda-cba6-4b91-b3f0-c042227e1cef
@kotlarmilos kotlarmilos added NO-MERGE The PR is not ready for merge yet (see discussion for detailed reasons) NO-REVIEW Experimental/testing PR, do NOT review it labels Sep 8, 2026
@azure-pipelines

Copy link
Copy Markdown
Azure Pipelines:
Successfully started running 3 pipeline(s).
13 pipeline(s) were filtered out due to trigger conditions.
There may be pipelines that require an authorized user to comment /azp run to run.

@dotnet-policy-service

Copy link
Copy Markdown
Contributor

Tagging subscribers to this area: @dotnet/runtime-infrastructure
See info in area-owners.md if you want to be subscribed.

@kotlarmilos

Copy link
Copy Markdown
Member Author

/azp run runtime-wasm

@azure-pipelines

Copy link
Copy Markdown
Azure Pipelines:
Successfully started running 1 pipeline(s).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area-Infrastructure NO-MERGE The PR is not ready for merge yet (see discussion for detailed reasons) NO-REVIEW Experimental/testing PR, do NOT review it

Projects

Status: No status

Development

Successfully merging this pull request may close these issues.

1 participant