One shared check now decides whether a run is non-interactive, covering print mode and piped output.
What's wrong with this entry?
A single helper now decides that a run is non-interactive, covering -p, --print, --init-only, any argument starting with --sdk-url, and stdout not being a terminal.
--init-only
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.229
A whitespace-only prompt gets its own error
Both mention print
-
v2.1.242
--printwith--cloudcan message an existing cloud sessionBoth mention print
-
v2.1.246
Project onboarding checklist gone
Both mention init