Update pinned SDK version to 10.0.102

[Copilot]

Description

Updates the pinned .NET SDK version from 10.0.101 to 10.0.102 to align with the latest SDK release. This prevents conflicts when developers have 10.0.102 installed globally but the repository pins to 10.0.101, which specifically affects dotnet dev-certs command execution.

If the SDK tooling version and the runtime version don't agree on the expected ASP.NET Core development certificate version, you can end up in a state where running dotnet dev-certs https --trust or dotnet dev-certs https --check --trust reports success, but you get runtime errors complaining about not being able to find a valid development certificate.

10.0.101 shipped with version 5 of the dev cert, while 10.0.102 includes version 6 (with support for 127.0.0.1 and ::1 addresses). This means that if global.json has our SDK and tools pinned to 10.0.101, but 10.0.102 is installed globally, running dotnet dev-certs https --trust or dotnet dev-certs https --check --trust from the Aspire repo would result in the certificate check passing as long as a version 5 certificate is present, but when you went to actually run the app host it would be using the latest version of the runtime that shipped with 10.0.102, which would expect to find a version 6 certificate.

While you can work around the issue by running dotnet dev-certs https --trust from a folder without a global.json, updating our versions helps avoid the potential pitfall altogether.

Changes

• Updated global.json SDK version from 10.0.101 to 10.0.102
  • sdk.version field
  • tools.dotnet field

Checklist

• Is this feature complete?
  • Yes. Ready to ship.
  • No. Follow-up changes expected.
• Are you including unit tests for the changes and scenario tests if relevant?
  • Yes
  • No
• Did you add public API?
  • Yes
    • If yes, did you have an API Review for it?
      • Yes
      • No
    • Did you add <remarks /> and <code /> elements on your triple slash comments?
      • Yes
      • No
  • No
• Does the change make any security assumptions or guarantees?
  • Yes
    • If yes, have you done a threat model and had a security review?
      • Yes
      • No
  • No
• Does the change require an update in our Aspire docs?
  • Yes
    • Link to aspire-docs issue (consider using one of the following templates):
      • New (or update) doc-idea template
      • New breaking-change template
      • New diagnostic template
  • No

Original prompt

---

This section details on the original issue you should resolve

<issue_title>Update the pinned SDK version to 10.0.102</issue_title>
<issue_description>The 10.0.102 SDK was just released; we need to update our global.json to reference the new SDK version to avoid potential headaches with running dotnet dev-certs commands from the aspire repo when the SDK is pinned to 10.0.101, but 10.0.102 is installed globally.</issue_description>

Comments on the Issue (you are @copilot in this section)

• Fixes Update the pinned SDK version to 10.0.102 #13935

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.

[radical]

/azp run aspire-tests

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[github-actions]

🚀 Dogfood this PR with:

⚠️ WARNING: Do not do this without first carefully reviewing the code of this PR to satisfy yourself it is safe.

curl -fsSL https://raw.githubusercontent.com/dotnet/aspire/main/eng/scripts/get-aspire-cli-pr.sh | bash -s -- 13936

Or

• Run remotely in PowerShell:

iex "& { $(irm https://raw.githubusercontent.com/dotnet/aspire/main/eng/scripts/get-aspire-cli-pr.ps1) } 13936"

[radical]

Once the aspire-tests azdo run completes, I can check whether this works fine there too. There will some unrelated test failures on azdo, so I will ignore those.

[Copilot]

Pull request overview

This PR updates the pinned .NET SDK version from 10.0.101 to 10.0.102 to align with the latest SDK release and prevent conflicts when developers have 10.0.102 installed globally.

Changes:

• Updated global.json SDK version from 10.0.101 to 10.0.102 in both the sdk.version and tools.dotnet fields

[radical]

/ba-g unrelated failures