publish: fix rich-from-R2 metadata jq (portable object-value grammar)#85
Merged
Conversation
…lue grammar)
The metadata.json synthesis used object-construction values with inline '+' and
'//' (vendor: ($sub[0].vendor // {name:$dn}) + {publisher_pubkey:$pub}). jq's
object-value grammar is stricter than a full pipe on some builds (CI's jq), which
rejected it with 'unexpected +, expecting }' — so a workflow_dispatch of a rich
submission failed after the bundle verified. Precompute the vendor + methods
sub-objects with plain jq and pass them as --argjson so every object value is a
single term. Verified in DRY_RUN against live R2 for insforge/orthogonal/didit.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
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
2 participants
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.
Follow-up to #84. A
workflow_dispatchof a rich submission (io.pilot.orthogonal) failed after the bundle verified, on the metadata.json synthesis:jq's object-construction value grammar is stricter than a full pipe on CI's jq build — inline
A + {..}/A // {..}as an object value isn't accepted. Fix: precompute thevendorandmethodssub-objects with plain jq and pass them as--argjson, so every value in the object literal is a single term (portable across jq 1.6/1.7/1.8). Re-validated inDRY_RUN=1against live prod R2 for insforge/orthogonal/didit.🤖 Generated with Claude Code