Merged
Conversation
Bump source-indexer's global.json from 10.0.100 to 10.0.101 as a contained mitigation for the current msbuild runtime mismatch while the broader prepare environment isolation fix proceeds separately. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> EOF && git push -u rf ankj/global-json-10-0-101 && gh pr create --repo dotnet/source-indexer --base main --head radical:ankj/global-json-10-0-101 --draft --title "Temporarily bump SDK to 10.0.101" --body-file - <<'EOF' ## Summary - bump `global.json` from `10.0.100` to `10.0.101` ## Why This is a contained temporary mitigation for the current `msbuild` mismatch, where repo-local SDK bits can end up using runtime state from the outer pipeline-installed dotnet. Installing `10.0.101` in the outer pipeline should make the hosted toolcache contain a runtime new enough to avoid the current `10.0.1` app-launch failure. This is intentionally separate from the broader fix in dotnet#249, which isolates inherited `.NET` environment variables during per-repo prepare. ## Validation - `dotnet --version`
Backport the explicit warning emission for per-repo prepare failures to the temporary global.json mitigation branch so failed repo prepares are visible without pulling in the full environment-isolation change. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Closed
jjonescz
approved these changes
Mar 13, 2026
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.
Summary
global.jsonfrom10.0.100to10.0.101Prepare All RepositoriesIssue
As discussed in #247, the failure was not that source-indexer itself needed a broad SDK upgrade. The problem was that the pipeline installed
.NET SDK 10.0.100, whilemsbuildbootstrapped and used.NET SDK 10.0.101in its repo-local.dotnet.That mismatch mattered because Roslyn from the
10.0.101SDK then resolved runtime state from the outer pipeline-installed dotnet location, which only hadMicrosoft.NETCore.App 10.0.0, not10.0.1. The result was themsbuildprepare failure seen in #247.Why this PR
This PR fixes that concrete failure by ensuring the outer pipeline-installed SDK/runtime matches the patch level needed by the current
msbuildbootstrap (10.0.101). In practice, that meansUseDotNet@2installs a runtime new enough to satisfy the currentmsbuildtoolset expectations.This change also keeps failed repo prepares visible by emitting explicit warnings instead of silently swallowing them.
Notes
A separate PR (#249) continues the broader environment-isolation work for per-repo prepare commands. That is still useful hardening, but this PR stands on its own as the direct SDK-version fix for the issue raised in #247.
Validation
dotnet --versionankj/global-json-10-0-101