Repository navigation
0.9.28
Linear can feed the factory's queue end to end (a tracker key, a Linear work source and queue backend, and write-back on ship and park), factory respond runs a feedback round on a factory PR, an issue whose prerequisite has an open PR builds a stacked PR on it, run-issue gains --in-place, --merge and per-run config overrides for disposable hosts, and SHIP syncs a branch onto main before opening its PR so sibling CHANGELOG bullets no longer strand drafts (#3872, #3894, #3910, #3916, #3904, #3905, #3906, #3945).
All seven published @on-par packages move to 0.9.28 in lockstep.
Install or update with npm install -g @on-par/factory-cli@latest.
Added
- Linear runs link their issue: the branch, PR title and body carry the key (
Fixes KEYon the final slice,Part of KEYbefore it), park, env-failure and slice-plan comments go to the Linear issue, the no-auto-merge hold reads Linear labels, and KPIs count Linear keys (#3894) - A queued issue whose prerequisite has an open factory PR now builds on it and opens a stacked PR against that branch, restacks onto main when the prerequisite merges or onto its new head when it moves, parks held when the prerequisite PR closes unmerged, and is never landed while its base is not main;
queue.stackOnOpenPrerequisite: falserestores waiting (#3916) - Feedback rounds: review rework reads all trusted PR feedback, re-plans on scope changes, replies to each item, resolves fixed threads and re-requests review;
factory respond <pr>starts one by hand (#3910) - Per-run config and constitution overrides:
--config/FACTORY_CONFIG_PATH/FACTORY_CONFIG_YAML,--constitution/FACTORY_CONSTITUTION_PATH/FACTORY_CONSTITUTION, and aFACTORY_CONFIG_OVERRIDESfragment; the run log andfactory doctorname the source (#3906). factory landresolves a CHANGELOG.md conflict confined to## Unreleasedby keeping main's entries and appending the PR's after them, and.gitattributesunions CHANGELOG.md on local merges (#3931).factory run-issue --mergeandrun-brief --mergedrive the PR through thefactory run --auto-mergegates to a merge, bounded by--merge-timeoutorci.awaitingCiCapHours, with distinct exit codes (0 merged, 10 held, 11 CI failed, 12 timed out, 13 land failed, 1 parked before a PR) (#3905)- The compile gate and
factory doctorfall back tonpm run typecheckwhen no build command resolves, and doctor names the detected test runner per workspace (#3913). factory runstarts lanes for work queued after it started, restarts finished lanes when new work arrives, and reaps expired claims mid-run; the interval isqueue.discovery_interval_ms(default 60s) (#3920)factory run-issue --in-place(orFACTORY_WORKSPACE=in-place) runs the pipeline in the current clean checkout with no worktree, for disposable containers (#3904).- With
tracker.kind: linear,factory run,factory superviseandfactory statustake their queue from Linear through one composedQueueBackend. A claim writes the first lease attachment, and lanes release a Linear claim they cannot build yet (#3918). - A run persists its resumable state (rework counters, handled reviews, status, spec summary) in a factory-owned PR comment and restores it on a fresh clone (#3909)
- Core has a Linear queue backend whose
listorders a lane's ready Linear issues by priority, order label and age, and whoseclaimNextclaims one with the claimed-by CAS; a Linear API error fails closed (#3892). - A
trackerconfig key selectsgithub(default) orlinearper repo, andfactory doctorchecks the Linear setup: a missing or rejectedLINEAR_API_KEYand any project with ready issues but no repo mapping (#3891). - Core has a read-only
linear-issuework source that resolvesON-12or a Linear issue URL into a work request; it readsLINEAR_API_KEYonly when used (#3889). - Core has a Linear queue lifecycle that releases, parks and reaps Linear claims, keeping the claim lease in a factory-owned attachment's metadata; a failed Linear write warns and never fails the run (#3893).
- Documented an OpenCode Go profile and recipe that pin DeepSeek V4 Pro as the PLAN (boss) model and V4 Flash as the BUILD/CHECK (worker/checker) models.
Fixed
- SHIP merges origin/main into the branch before it pushes a PR against main, auto-resolving
## UnreleasedCHANGELOG and ADR index conflicts asfactory landdoes, so a sibling's CHANGELOG bullet no longer leaves the PR conflicting with no CI and stranded as a CI-pending draft; a conflict it cannot resolve is aborted and the branch ships unsynced as before (#3945). - CHECK follows a root workspace fan-out
testscript into the owning npm/pnpm/yarn workspace and runs fail-to-pass selectors there with vitest or jest (#3913).
Changed
- Lanes,
factory superviseand thefactory statusqueue band claim, heartbeat, release and list through the WorkKey queue seam, and run state is written with a stringkey. A GitHub issue's record also keeps its numericissue, so a factory 0.9.27 or earlier on the same host still reads it (#3890). - The queue's claim-time prerequisite defer also reads
Depends on: #Nlines, and bothDepends on:andPrerequisite:accept a comma list such as#3891, #3892(#3915). - The OpenCode supported version range widens to
>=1.18.0 <2.3.0, so OpenCode 2.x (tested at 2.2.5) no longer triggers a doctor warning.
Fixed
- The factory-run workflow uploads
.factory/state/events.ndjson, verify fails when thefactory --helpfixture is stale, and help text, runbooks and the config example (stack mode builds every slice in one run for run-issue and run-brief) match the CLI (#3921).