-
Notifications
You must be signed in to change notification settings - Fork 278
Comparing changes
Open a pull request
base repository: dotnet/dotnet
base: 840ea13
head repository: dotnet/dotnet
compare: 491bbab
- 12 commits
- 1,111 files changed
- 5 contributors
Commits on Mar 21, 2026
-
Configuration menu - View commit details
-
Copy full SHA for 5852d1c - Browse repository at this point
Copy the full SHA 5852d1cView commit details -
Configuration menu - View commit details
-
Copy full SHA for d86ad7e - Browse repository at this point
Copy the full SHA d86ad7eView commit details -
Set RequiresDelayedBuild=true for LinkabilityChecker.csproj
Something changed in the build ordering so that LinkabilityChecker runs before the actual assemblies are built. This seems like a longstanding problem that just wasn't noticed before, setting RequiresDelayedBuild enforces LinkabilityChecker builds after the shared framework.
Configuration menu - View commit details
-
Copy full SHA for a13417d - Browse repository at this point
Copy the full SHA a13417dView commit details -
Configuration menu - View commit details
-
Copy full SHA for d610801 - Browse repository at this point
Copy the full SHA d610801View commit details
Commits on Mar 22, 2026
-
Fix LinkabilityChecker build ordering via Arcade BuildStep
LinkabilityChecker's delayed build depends on trimmable project outputs, but Arcade's batch-based build system (not solution graph) provides no ordering guarantee within the same BuildStep. All managed projects, including BuildAfterTargetingPack, were in BuildStep='managed' and built in parallel — a nondeterministic scheduling change in the new SDK caused LinkabilityChecker to run before its dependencies were built (IL1032). Move BuildAfterTargetingPack to BuildStep='post-managed' in Build.props so Arcade's target batching guarantees all managed projects complete before delayed builds (like LinkabilityChecker) start. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Configuration menu - View commit details
-
Copy full SHA for 29be5dc - Browse repository at this point
Copy the full SHA 29be5dcView commit details -
Configuration menu - View commit details
-
Copy full SHA for 1c6d26d - Browse repository at this point
Copy the full SHA 1c6d26dView commit details -
[main] Source code updates from dotnet/runtime (#5588)
[main] Source code updates from dotnet/runtime
Configuration menu - View commit details
-
Copy full SHA for 74c3eaa - Browse repository at this point
Copy the full SHA 74c3eaaView commit details -
[runtime] Source update ebb0dea → be2631f
Diff: https://github.com/dotnet/runtime/compare/ebb0dea8739963992b38dae9a60185da2802d8d0..be2631fa380635f4e357ccdd0d140e2a8069800b From: dotnet/runtime@ebb0dea To: dotnet/runtime@be2631f [[ commit created by automation ]]
Configuration menu - View commit details
-
Copy full SHA for c15a55e - Browse repository at this point
Copy the full SHA c15a55eView commit details
Commits on Mar 23, 2026
-
Configuration menu - View commit details
-
Copy full SHA for fcc3bc5 - Browse repository at this point
Copy the full SHA fcc3bc5View commit details -
[main] Source code updates from dotnet/sdk (#5556)
[main] Source code updates from dotnet/sdk
Configuration menu - View commit details
-
Copy full SHA for bebe99a - Browse repository at this point
Copy the full SHA bebe99aView commit details -
[main] Source code updates from dotnet/runtime (#5629)
[main] Source code updates from dotnet/runtime
Configuration menu - View commit details
-
Copy full SHA for 7c48c5b - Browse repository at this point
Copy the full SHA 7c48c5bView commit details -
[main] Source code updates from dotnet/aspnetcore (#5628)
[main] Source code updates from dotnet/aspnetcore
Configuration menu - View commit details
-
Copy full SHA for 491bbab - Browse repository at this point
Copy the full SHA 491bbabView commit details
This comparison is taking too long to generate.
Unfortunately it looks like we can’t render this comparison for you right now. It might be too big, or there might be something weird with your repository.
You can try running this command locally to see the comparison on your machine:
git diff 840ea13...491bbab