[release/10.0.1xx] Fix first-run experience output interfering with completion commands #50472
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]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
Co-authored-by: baronfel <[email protected]>
Co-authored-by: baronfel <[email protected]>
…d of stdout Co-authored-by: baronfel <[email protected]>
…ser test and update copilot-instructions with test running guidance Co-authored-by: baronfel <[email protected]>
baronfel
added
Review for breaking changes
needs-breaking-change-doc-created
Area-CLI
breaking-change
|
Added When you commit this breaking change:
You can refer to the .NET SDK breaking change guidelines |
3 tasks
SimonZhao888
approved these changes
Aug 26, 2025
|
Mail sent and Breaking Change PR created. |
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 #50454 to release/10.0.1xx
/cc @baronfel @copilot
Since this is a behavioral breaking change for Powershell users below a certain version, I'm going to tag this for a breaking change doc/email so we can point those users to the newer powershell setting to make stderr output not automatically get lifted into powershell errors.