Skip to content

fix(ci): consolidate qualification and preserve runtime caches - #230

Merged
f0rr0 merged 3 commits into
mainfrom
f0rr0/simplify-ci-release-reuse
Oct 1, 2026
Merged

f0rr0 merged 3 commits into
mainfrom
f0rr0/simplify-ci-release-reuse

Conversation

@f0rr0

@f0rr0 f0rr0 commented Oct 1, 2026 •

Copy link
Copy Markdown
Owner

Summary

A transient GitHub error while inspecting qualification could request another CI run. Selecting database resources could also produce an empty native desktop matrix. Retry unresolved inspection before dispatch, and derive directly selected producers from Moon's declared job targets so all released products follow the same selection rules.

Restoring the Cargo cache also creates runtime/wasmer/target before the source checkout. Git clone then fails on the nonempty parent on Linux and macOS ARM64, including every rerun. Initialize and fetch the exact verified local sources in place, preserving cached outputs for the runtime and nested checkouts.

  • Use one shared packaging input group that excludes tests. Keep test suites affected, and limit WASIX runtime packaging to the release modules it actually imports.
  • Reuse the original release plan and completed-run metadata across preparation, bootstrap and publication. Remove duplicate step guards, the redundant bootstrap scope step, and unused release-job Moon output caches.
  • Partition active Moon caches by task group and target. Remove the unused producer ancestry pilot and its extra API read and validation.
  • Avoid duplicate frozen-file reads and hashes while preserving archive validation, atomic installation and byte verification. Narrow Postmaster inputs to its own Cargo workspaces and Rust pin, and correct recovery documentation.

Release Intent

  • Package/API/runtime change: PR title uses fix:.
  • Source/input/runtime asset change: exact source pins and release metadata remain current.

Verification

Using Moon 2.5.4 and Bun 1.4.2:

  • Full workflow gate: actionlint, zizmor, planning, cache, security and artifact-transfer checks.
  • Release mutation suite, metadata checks, Release Please candidate integration, and affected TypeScript formatting/lint.
  • 55 selection cases: all 27 products individually, every database-resource pairing, and the complete set in both orders; exact product coverage and required task closure hold.
  • Actual Moon queries confirm shared packaging tests and unrelated release controllers select checks without product builders; production helpers still affect their consumers.
  • Artifact downloader behavior verifies cached metadata reuse, exact identities, retries, atomic promotion and corruption rejection.
  • Waiter and publication-controller behavior under Bash 3.2.57; original and simplified capsule implementations produce byte-identical archives.
  • Cache-restore regression: the original source preparation fails, while the fix preserves outputs and exact pins on initial, repeated and forced preparation under current Bash and Bash 3.2.57.
  • Postmaster owner lint and full unit suite.
  • Hosted CI on the updated PR commit.

@vercel

vercel Bot commented Oct 1, 2026 •

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated
oliphaunt-docs Ready Ready Preview Oct 1, 2026 9:52pm UTC

@f0rr0 f0rr0 changed the title fix(ci): consolidate qualification reuse and publication planning fix(ci): consolidate qualification and release preparation Oct 1, 2026
@f0rr0 f0rr0 changed the title fix(ci): consolidate qualification and release preparation fix(ci): consolidate qualification and preserve runtime caches Oct 1, 2026
@f0rr0
f0rr0 marked this pull request as ready for review October 1, 2026 21:55
@f0rr0
f0rr0 merged commit 79c3409 into main Oct 1, 2026
120 checks passed
@f0rr0
f0rr0 deleted the f0rr0/simplify-ci-release-reuse branch October 1, 2026 23:40

This branch was successfully deployed

1 active deployment
Preview — 60ca7ddd Deployed Oct 1, 2026 by vercel[bot]
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant