Repository navigation
0.9.27
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
previewconfig: after CI is green, SHIP finds the PR's preview (deployment status, or a PR comment from an allow-listed author viaauthors/authorAssociationsthat names or postdates the head commit), waits for it, runs a smoke command withPREVIEW_URL, and sends fail orpreview-unavailableback to rework. Only public http(s) hosts are probed:readyPathmust 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 topreview-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/testingexportscreateFakeGitHubandgithubError: a realOctokitanswered by an in-memory route table, so tests can fake GitHub with strict types (#3880).factory classifier report(and--jsonastier) shows trust-tier promotion evidence: configured tier, coverage ratchet, per-package mutation vs floor, human-intervention rate with a caveat, rule-of-three slips andeligibleForwith the unmet criteria; missing or stale evidence isunknown, never 0%;npm run coverage-ratchet -- --out coverage-ratchet.jsonwrites 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-demotionrestores 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 parksfail(#3880). - An unknown
sizeGate.mode(for exampleOff,none,bogus) still runs as stack but now warns at config load and run start, and shows a non-failing⚠️ factory doctorrow naming the value andoff, stack(#3850). - A CHECK environment release whose fresh base re-run fails while GitHub CI is green now writes a
confirmedLocallybase hold, so the lane no longer re-claims and rebuilds the issue every poll;factory statusnames the waiting issue (#3851). factory resume N --from checkrefuses with both SHAs andfactory run-issue Nwhen origin's default branch moved since the build was kept, instead of re-checking on the stale base; the preserved-build hint points atrun-issuefor 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
skippedorneutralrequired check as passing, like GitHub, so a skipped check on main no longer writes a permanent merge pause or markshosted-cifailing; an existing pause clears on the next check (#3871).
Changed
npm run mutationnow 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 hostedcommands and hosted control plane and runner exports; contained fork-PR review is unchanged. @on-par/factory-coreno longer exportsFactoryConfigV2Schema,factoryConfigV2JsonSchema,loadV2ConfigandparseV2Config; no shipped command read them and repo config is unchanged (#3444).