seed-release: jq → node; reseed no-op guard ignores mitosis self-ref #131
No reviewers
Labels
No labels
bug
discussion
duplicate
enhancement
goal
help wanted
horizon:backlog
horizon:governance
horizon:mvp
invalid
operator-decision
question
roadmap
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
open-platform/mitosis!131
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "fix/seed-release-jq"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Two robustness fixes from watching the merged flow run:
jq— the isolated runner image ships node/bun but no jq (the same trapreseed-run.shdocuments for the vxrail host). JSON payload/parse now usesnode -e. No behavior change otherwise.Validation on merge: the open r286 reseed PR's eventual merge fires the fixed seed-release → expect tag
seed-r286, a Release with tarball+manifest attached, and the seed package auto-linked to this repo's Packages tab.🤖 Generated with Claude Code
Superseded by #266 (merged): seed-release is now jq-free (curl/sed/tr/tar only — the isolated runner image ships no jq, which was the root cause of every failure, #263), tags come from genesis/upstream.json
.release, API calls go in-cluster, and both lanes are proven — dispatch created seed-r886, the r897 reseed push created seed-r897. Closing.Pull request closed