Skip to content

0.9.27

Choose a tag to compare

@patrob patrob released this 03 Nov 19:02
· 185 commits to main since this release
5be5415

An opt-in preview gate checks a PR against its preview environment, SHIP fails closed when the CI watch itself fails, and trust-tier promotion evidence and demotion are recorded (#3880, #1957, #1959).
All seven published @on-par packages move to 0.9.27 in lockstep.
Install or update with npm install -g @on-par/factory-cli@latest.

Added

  • Opt-in preview config: after CI is green, SHIP finds the PR's preview (deployment status, or a PR comment from an allow-listed author via authors / authorAssociations that names or postdates the head commit), waits for it, runs a smoke command with PREVIEW_URL, and sends fail or preview-unavailable back to rework. Only public http(s) hosts are probed: readyPath must stay on the preview host, the probe connects only to the address the host check approved, and the host is checked again right before the smoke command starts. CI still pending, or a CI watch that fails, fails the gate closed. Evidence goes to preview-check.json (also when the gate throws), artifacts are copied into the run logs, and the result is written to the PR body (#3880).
  • @on-par/factory-core/testing exports createFakeGitHub and githubError: a real Octokit answered by an in-memory route table, so tests can fake GitHub with strict types (#3880).
  • factory classifier report (and --json as tier) shows trust-tier promotion evidence: configured tier, coverage ratchet, per-package mutation vs floor, human-intervention rate with a caveat, rule-of-three slips and eligibleFor with the unmet criteria; missing or stale evidence is unknown, never 0%; npm run coverage-ratchet -- --out coverage-ratchet.json writes the coverage evidence (#1957).
  • A post-merge defect on a PR auto-merged under trust tier T1 or T2 records a tier demotion, lowers the effective tier one step, and comments once on the defect issue; factory classifier ack-demotion restores the configured tier (#1959).

Fixed

  • SHIP no longer marks a PR ready for review when the CI watch itself fails, for example on a GitHub API error. CI counts as unknown: SHIP fails with CI unknown for PR #N: the CI watch failed (...), the PR is not marked ready, also in draft mode, and the run parks fail (#3880).
  • An unknown sizeGate.mode (for example Off, none, bogus) still runs as stack but now warns at config load and run start, and shows a non-failing ⚠️ factory doctor row naming the value and off, stack (#3850).
  • A CHECK environment release whose fresh base re-run fails while GitHub CI is green now writes a confirmedLocally base hold, so the lane no longer re-claims and rebuilds the issue every poll; factory status names the waiting issue (#3851).
  • factory resume N --from check refuses with both SHAs and factory run-issue N when origin's default branch moved since the build was kept, instead of re-checking on the stale base; the preserved-build hint points at run-issue for fixes that land on main and only names log paths that exist (#3852).
  • Land no longer stalls when a required check only runs on pull requests: a required context with no run on the base head is treated as no hosted base signal, merges proceed after a short grace and one warn event names the context (#3870).
  • The base CI gate and base health treat a skipped or neutral required check as passing, like GitHub, so a skipped check on main no longer writes a permanent merge pause or marks hosted-ci failing; an existing pause clears on the next check (#3871).

Changed

  • npm run mutation now mutates the merge-gating review modules (floor, risk, verdict, routing) on Stryker 10.1.1, which runs mutants correctly under Vitest 5.

Removed

  • Removed the experimental discovery exports from @on-par/factory-core.
  • Removed the unpublished dashboard and server packages; no shipped command used them.
  • Removed the experimental, flag-gated factory hosted commands and hosted control plane and runner exports; contained fork-PR review is unchanged.
  • @on-par/factory-core no longer exports FactoryConfigV2Schema, factoryConfigV2JsonSchema, loadV2Config and parseV2Config; no shipped command read them and repo config is unchanged (#3444).