seed-release: jq → node; reseed no-op guard ignores mitosis self-ref #131

Closed
plat wants to merge 1 commit from fix/seed-release-jq into main
Owner

Two robustness fixes from watching the merged flow run:

  1. seed-release's first run (on the r278 merge) died on a bare jq — the isolated runner image ships node/bun but no jq (the same trap reseed-run.sh documents for the vxrail host). JSON payload/parse now uses node -e. No behavior change otherwise.
  2. The reseed no-op guard now excludes mitosis's own ref from the refs comparison: every reseed merge moves mitosis main by exactly one genesis commit, so including it makes the nightly cron see "drift" forever and open a self-referential churn PR every day. With the exclusion, the cron is quiet unless a sibling system repo actually moved.

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

Two robustness fixes from watching the merged flow run: 1. **seed-release's first run (on the r278 merge) died on a bare `jq`** — the isolated runner image ships node/bun but no jq (the same trap `reseed-run.sh` documents for the vxrail host). JSON payload/parse now uses `node -e`. No behavior change otherwise. 2. **The reseed no-op guard now excludes mitosis's own ref** from the refs comparison: every reseed *merge* moves mitosis main by exactly one genesis commit, so including it makes the nightly cron see "drift" forever and open a self-referential churn PR **every day**. With the exclusion, the cron is quiet unless a sibling system repo actually moved. 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](https://claude.com/claude-code)
seed-release: jq -> node (isolated image has no jq); reseed: no-op guard ignores mitosis self-ref
All checks were successful
guard-ppt / no-ppt (push) Successful in 10s
guard-ppt / no-ppt (pull_request) Successful in 11s
e67d264d86
The first seed-release run died on a bare jq — the isolated runner
ships node/bun but no jq (same trap reseed-run.sh documents for the
vxrail host). And the reseed no-op guard now excludes mitosis's own
ref: every reseed MERGE moves mitosis main by one genesis commit, so
including it would make the nightly cron open a churn PR every day.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Author
Owner

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.

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.
plat closed this pull request 2026-09-02 15:30:50 +00:00
All checks were successful
guard-ppt / no-ppt (push) Successful in 10s
Required
Details
guard-ppt / no-ppt (pull_request) Successful in 11s
Required
Details

Pull request closed

Sign in to join this conversation.
No description provided.