[release/2025-10B] Do not restore for dotnet run scenario in tests#6719
Merged
lbussell merged 1 commit intoOct 14, 2025
Merged
Conversation
lbussell
changed the title
dotnet run scenario in testsdotnet run scenario in tests
mthalman
approved these changes
Oct 14, 2025
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.
This change adds the
--no-restoreflag todotnet runscenarios in the container image tests. This prevents thedotnet runcommand from reaching out to NuGet during the Blazor WASMdotnet runscenario test. Thedotnet runscenario does not use NuGet authentication so it can't reach internal package feeds during internal builds/tests.