Fix publish summary rendering "❓ no result" for every package - #196
Merged
Conversation
Root cause: gh api leaks its raw error body (with embedded quotes) to
stdout on 404s for brand-new packs, and that raw value was interpolated
directly into a jq --arg via ${{ }}, breaking the quoting and corrupting
the whole jq invocation into writing a bare boolean instead of a JSON
object. That single malformed fragment then aborted jq for every cell.
Co-authored-by: felickz <1760475+felickz@users.noreply.github.com>
Copilot
AI
changed the title
Fix publish summary showing "❓ no result" for every package in v0.7.1 release notes
Fix publish summary rendering "❓ no result" for every package
Jul 28, 2026
Copilot created this pull request from a session on behalf of
felickz
July 28, 2026 05:02
View session
Co-authored-by: felickz <1760475+felickz@users.noreply.github.com>
felickz
marked this pull request as ready for review
July 28, 2026 05:27
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.
The v0.7.1 release notes showed "❓ no result" across the entire publish summary table, even though every package (including the new
go/pythonextpacks) published successfully.Root cause
Publishing a brand-new pack for the first time triggers a 404 from
gh api, which prints its raw, unfiltered error body to stdout even with--jqand2>/dev/null. That JSON body's embedded quotes leaked through a step output and got interpolated directly via${{ }}into ajq --arginvocation, breaking its quoting and corrupting the whole call into emitting a baretrue/falseinstead of a JSON object. The summary script then indexed that stray boolean while iterating all fragments, aborting the render for every cell instead of just the broken ones.Changes
check_versionsteps (all 4 publish jobs): forcePUBLISHED_VERSIONempty on anygh apifailure instead of relying on2>/dev/null || true, which doesn't stop a leaked stdout error body.Record publish resultsteps (all 4 publish jobs): passprevious_version/target_versionthroughenv:and reference them as shell variables instead of interpolating${{ }}directly into thejq --argline, so embedded quotes can no longer corrupt the invocation.build-publish-summary.sh: filter out non-object fragments incell()so one malformed result only affects its own cell instead of the entire table.