Skip to content

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 into
microsoft:mainfrom
DmitriyShepelev:sfi-es5.2/dotnet-sdk-10.0.103-patch
May 29, 2026
Merged

Meera Ruxmohan (mruxmohan4) merged 2 commits into
microsoft:mainfrom
DmitriyShepelev:sfi-es5.2/dotnet-sdk-10.0.103-patch

Conversation

@DmitriyShepelev

Copy link
Copy Markdown
Collaborator

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

- "version": "10.0.100",
+ "version": "10.0.103",

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 build compiles all projects successfully against locally-installed SDK 10.0.300 (satisfies the new pin via rollForward: latestMajor). The build returns a non-zero exit at the very end on Microsoft.VisualStudio.SlnGen.Extension.csproj with VSIX deployment is not supported with 'dotnet build' — this is pre-existing on main@d5363e1 (VSIX requires full MSBuild.exe) and unrelated to this SDK bump.

Compliance metadata

  • KPI: SFI-ES5.2
  • Advisory: DOTNET-Security-10.0
  • S360 service ID: 9456803b-2bcc-42dd-aa63-caff3ea00dcd (rolls up under CloudBuild.Tools.MSBuild)

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>
@DmitriyShepelev
Dmitriy Shepelev (DmitriyShepelev) marked this pull request as ready for review May 28, 2026 21:02
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>
@DmitriyShepelev
Dmitriy Shepelev (DmitriyShepelev) force-pushed the sfi-es5.2/dotnet-sdk-10.0.103-patch branch from 27680f8 to c12fa53 Compare May 29, 2026 13:50
@DmitriyShepelev

Copy link
Copy Markdown
Collaborator Author

/azp run

@azure-pipelines

Copy link
Copy Markdown
Commenter does not have sufficient privileges for PR 717 in repo microsoft/slngen

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants