Repository navigation
SFI-ES5.2: bump .NET SDK pin 10.0.100 -> 10.0.103 (DOTNET-Security-10.0) - #717
Merged
Meera Ruxmohan (mruxmohan4) merged 2 commits intoMay 29, 2026
Conversation
Addresses S360 advisory DOTNET-Security-10.0 by moving the global.json `sdk.version` pin to the minimum patched SDK within the existing 10.0.1xx feature band. Source: dotnet/core release-notes/10.0/releases.json entry for release 10.0.3 (sdk 10.0.103, security=true, 2026-02-10). KPI: SFI-ES5.2 Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Dmitriy Shepelev (DmitriyShepelev)
marked this pull request as ready for review
May 28, 2026 21:02
Andy Gerlicher (AndyGerlicher)
approved these changes
May 28, 2026
Andy Gerlicher (AndyGerlicher)
enabled auto-merge (squash)
May 28, 2026 21:17
auto-merge was automatically disabled
May 29, 2026 13:49
Head branch was pushed to by a user without write access
…ding The previous commit bumped the hardcoded `-version 10.0.100` to `10.0.103` in both azure-pipelines.yml (PR CI) and azure-pipelines-official.yml (official build) so that the dotnet-install.ps1 invocation matches the new global.json pin. Hardcoding is brittle — every future global.json bump requires touching both pipelines or CI fails with `A compatible .NET SDK was not found` (as happened on the first push of this PR). Switching to `-JSonFile global.json` makes dotnet-install.ps1 read sdk.version directly from the repo, so the pipeline stays in lockstep with global.json automatically. KPI: SFI-ES5.2 Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Dmitriy Shepelev (DmitriyShepelev)
force-pushed
the
sfi-es5.2/dotnet-sdk-10.0.103-patch
branch
from
May 29, 2026 13:50
27680f8 to
c12fa53
Compare
Collaborator
Author
|
/azp run |
|
Commenter does not have sufficient privileges for PR 717 in repo microsoft/slngen |
Meera Ruxmohan (mruxmohan4)
approved these changes
May 29, 2026
Dmitriy Shepelev (DmitriyShepelev)
deleted the
sfi-es5.2/dotnet-sdk-10.0.103-patch
branch
May 29, 2026 17:02
This was referenced Sep 29, 2026
Merged
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
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.
Bumps the .NET SDK pin in global.json from 10.0.100 to 10.0.103 to remediate advisory DOTNET-Security-10.0.
Why
10.0.103 is the minimum-patched SDK in the 10.0.1xx feature band (security release 2026-02-10,
security: true). Sourced from the official channel feed:Strategy: minimum-patched in the 10.x major; did not cross feature bands or majors.
Diff
ollForward: latestMajor is already in place, so existing dev/CI environments with 10.0.10x+ continue to work without action.
Risk
LOW — patch-band bump only; no API/behavior changes within a .NET SDK patch release.
Validation
dotnet buildcompiles all projects successfully against locally-installed SDK 10.0.300 (satisfies the new pin viarollForward: latestMajor). The build returns a non-zero exit at the very end onMicrosoft.VisualStudio.SlnGen.Extension.csprojwithVSIX deployment is not supported with 'dotnet build'— this is pre-existing onmain@d5363e1(VSIX requires fullMSBuild.exe) and unrelated to this SDK bump.Compliance metadata
9456803b-2bcc-42dd-aa63-caff3ea00dcd(rolls up under CloudBuild.Tools.MSBuild)