[release/13.1] Ensure we install a consistent .NET SDK version between ./dotnet.sh and actions/setup-dotnet #13477
Conversation
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
github-actions
bot
requested review from
eerhardt and
radical
as code owners
dotnet-policy-service
bot
added
Re-opened Github-Action PR
and removed
Closed Github-Action PR
labels
Contributor
Author
|
🚀 Dogfood this PR with:
curl -fsSL https://raw.githubusercontent.com/dotnet/aspire/main/eng/scripts/get-aspire-cli-pr.sh | bash -s -- 13477Or
iex "& { $(irm https://raw.githubusercontent.com/dotnet/aspire/main/eng/scripts/get-aspire-cli-pr.ps1) } 13477" |
JamesNK
approved these changes
Dec 10, 2025
eerhardt
approved these changes
Dec 11, 2025
joperezr
added
Servicing-approved
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.
Backport of #13468 to release/13.1
/cc @danegsta
Customer Impact
This fixes a test failure due to a mismatched local 10.0.101 SDK and a repo specific 10.0.100 SDK that was used for certificate trust. 10.0.101 added a new dev cert revision, which resulted in the system trusting the older 10.0.100 certificate, but the certificate version from 10.0.101 being used by Aspire. This is a build infrastructure only change.
Testing
Re-enabled the failing test.
Risk
Low
Regression?