fix: withdraw the interactive fusion transition notice - #158
Merged
Conversation
Default recon <domain> stays silent. Fusion remains enabled when neither flag is supplied. --fusion and --no-fusion still pin the diagnostic.
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
1 participant
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.
Default
recon <domain>no longer prints a fusion-flag deprecation notice.v2.18.3 reworded that TTY nags so it no longer promised a v3 flip. The implicit default is still not scheduled to change, so asking every interactive run to pin
--fusionor--no-fusionis leftover process. This withdraws the notice.--fusionand--no-fusionstill pin the diagnostic on or off.--no-fusionselects deterministic output.Changelog is dated for 2.18.4 so the existing release script can cut the patch after merge.