Conversation
github-actions
Bot
added
core
releases-note/fix
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.
Which issue does this PR close?
No linked issue.
Rationale for this change
Release verification discards Cargo stderr and both Maven output streams. Long builds provide no progress, and failures hide the underlying diagnostics behind a subprocess exit error.
What changes are included in this PR?
Let Cargo and Maven inherit the verification script's output streams, flush build-start messages before launching them, and update the verification guide.
Are there any user-facing changes?
Users can see build progress and error messages while verifying source packages. Build commands and failure handling remain unchanged.
Validated by building core and the Java binding from locally generated unsigned source archives on macOS. Both builds completed successfully. Java tests remain skipped by the existing verification command; signature verification was not exercised.
Breaking changes
AI Usage Statement
Codex with GPT-6-Astra