Skip to content

Conversation

@akoeplinger
Copy link
Member

@akoeplinger akoeplinger commented Nov 24, 2025

Backport of #121923

Customer Impact

.NET 10 builds from the VMR (dotnet/dotnet) instead of dotnet/runtime. Source maps generated during CI builds were pointing to the old repository, causing 404 errors when browser debuggers attempted to load TypeScript sources.

Regression

  • Yes
  • No

This regressed when the official runtime build moved to happen in the VMR.

Testing

Local testing to make sure the correct URL is produced.

Risk

Low. This only affects debugging scenarios.

Copilot AI review requested due to automatic review settings November 24, 2025 15:35
@github-actions github-actions bot added the needs-area-label An area label is needed to ensure this gets routed to the appropriate area owners label Nov 24, 2025
@akoeplinger akoeplinger added Servicing-consider Issue for next servicing release review arch-wasm WebAssembly architecture area-Build-mono and removed needs-area-label An area label is needed to ensure this gets routed to the appropriate area owners labels Nov 24, 2025
Copilot finished reviewing on behalf of akoeplinger November 24, 2025 15:37
Copy link
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR fixes source map URLs for .NET 10 builds to point to the new VMR (Virtual Monolithic Repository) structure. When browser debuggers attempt to load TypeScript sources during debugging, they were receiving 404 errors because the URLs pointed to the old dotnet/runtime repository instead of the new dotnet/dotnet repository.

Key changes:

  • Updated the source map URL generation to use the dotnet/dotnet repository with the appropriate path prefix /src/runtime/

@rbhanda rbhanda added this to the 10.0.2 milestone Nov 24, 2025
@rbhanda rbhanda added Servicing-approved Approved for servicing release and removed Servicing-consider Issue for next servicing release review labels Nov 24, 2025
@akoeplinger
Copy link
Member Author

/ba-g failures in WasmBuildTests are unrelated

@revbones-dev
Copy link

Is there a workaround or timeframe to receive this?

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

Labels

arch-wasm WebAssembly architecture area-Build-mono Servicing-approved Approved for servicing release

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants