fix(version): write update notices to stderr for JSON-safe output#68
Merged
andrasbacsai merged 1 commit intov4.xfrom Mar 30, 2026
Merged
fix(version): write update notices to stderr for JSON-safe output#68andrasbacsai merged 1 commit intov4.xfrom
andrasbacsai merged 1 commit intov4.xfrom
Conversation
Redirect the version update message from stdout to stderr so command JSON output stays machine-readable. Expand checker tests with shared stdout/stderr capture helpers and assertions to verify: - update notices are emitted on stderr only - stdout remains clean during checks and errors - JSON output to stdout is unaffected when an update is available
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
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.
Summary
stderrinstead ofstdoutin the version checker.stdoutoutput for--format jsonand automation pipelines.stdout/stderrcapture helper and add assertions for stream separation, including a JSON passthrough scenario.Breaking Changes
Fixes #66