fix(publish): route publish status messages to stderr#39
Merged
fullstackjam merged 1 commit intomainfrom Apr 21, 2026
Merged
Conversation
TestE2E_Publish_UpdateViaSyncSource asserts the "Publishing to @user/slug (updating)" message lands on stderr, but ui.Info prints via fmt.Println to stdout. Every other line in publishSnapshot (surrounding blank lines, the final success marker) already goes through os.Stderr, so the ui.Info calls were the lone stream mismatch and blocked the destructive-test gate in the release workflow since v0.55.1. Write both publish-status lines directly to os.Stderr, matching the rest of the publish output stream and unblocking releases.
|
👋 Thanks for opening this pull request! Before merging:
@fullstackjam will review this soon. Thanks for contributing! 🚀 |
Codecov Report❌ Patch coverage is
📢 Thoughts on this report? Let us know! |
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.
Summary
Fixes the destructive-test gate in the release workflow, which has been blocking releases since v0.55.1 (run 24733624876 was the v0.55.2 failure).
TestE2E_Publish_UpdateViaSyncSource(test/e2e/publish_import_e2e_test.go:234) asserts thePublishing to @user/slug (updating)message lands on stderr, butui.Infoprints viafmt.Printlnto stdout. The surrounding blank-line writes and the final✓ Config published successfully!marker already useos.Stderr, so the twoui.Infocalls were the lone stream mismatch.Fix: write both publish-status lines directly to
os.Stderr, matching the rest of the publish output stream.Test plan
gate-tests→ Destructive tests step passes on macos-latestopenboot snapshot --publish(with a saved sync source) still shows the "Publishing to @…" line to the user