Current
Check the tree you named.
ArkGate 4.8.26 is on npm latest. Patch over 4.8.25 (#353, #354). No required config migration: a config that loads in 4.8.25 still loads. That is Contener · Guiar · Ordenar.
Upgrade
Install 4.8.26
No required config migration. No schema bump. No new config fields. Does not close K01 or Z09. This mother config still does not turn ArkOrder on.
What shipped
The directory is the tree. The path is a file.
--root is the analyzed tree (#353)
ark-check --root <dir> --config <file>
analyzes <dir>. An explicit
--config path is a file. Layer patterns resolve
against that directory. The folder that holds the file never
becomes the tree, inside --root, beside it, or
on an absolute path (#353, #352).
A pass is a pass of that tree
A config outside --root used to make the check
read the config’s folder, and it could print a pass for a
tree it never opened. That swap is gone. A contract that
matches nothing in --root still refuses with
ANALYSIS_COVERS_NO_FILES. A missing
ark.config.json may still adopt an ancestor
contract, and that ancestor contains the directory you
named. The 4.8.11 rule for a nested config inside
--root now holds for an explicit path outside it.
--strict on every branch (#354)
--strict and --strict-merge refuse
a policy config outside the Git repository before they look
for a base ref. The refusal runs on every branch, including
the trunk. The message stays
Policy config must be inside the Git repository
(exit 2). On main, discovery used to find no
predecessor and skip that refusal, so the same command could
exit 0.
Behavior
What still analyzes the tree.
-
A check without
--strictstill analyzes--root.--strict-configstill analyzes--root. -
An explicit
--policy-basefile stays allowed. It is a file you named, and the Git-repository refusal does not apply to it. - No new flag. No new message. The refusal text is the one 4.8.25 already printed once a base ref had been found.
Honesty
What stayed the same.
No schemaVersion bump. No required config migration.
Does not close K01 or Z09. Import rules still hold at write and
at merge. Required CI is still the hard line. ArkOrder stays
opt-in.
Maintainer source: CHANGELOG.md ↗