Skip to content

v0.2.4

Choose a tag to compare

@fioenix fioenix released this 11 Nov 04:23
· 983 commits to main since this release
1600861

v0.2.4 - 2026-11-11

Highlights

This release helps you check your work when cloud CI is expensive or out of minutes, and makes updating the plugin walk you through what is new.

  • Repository checks. /fnl-setup add checks finds a repository's checks and saves the list you approve. checks.py run runs it locally, with an optional pre-push hook.
  • A local receipt when cloud CI cannot run. Opt in per repository, and a passing full run can stand in for missing or failing cloud checks at the merge gate. It is self-reported, so it suits a repository one person works on.
  • Cheaper CI. Setup can write a GitHub Actions workflow that skips document-only changes and cancels superseded runs, and checks.py usage shows what your CI minutes cost.
  • Guided updates. /fnl-update now goes on to a checklist of what the new version adds; /fnl-update whats-new only shows it. You can also pick or pin a version.
  • Renamed. fnl-verification is now fnl-checks; the old name keeps working through 0.2.x.

Not verified on a live host: a real git push through the installed hook, and a run of the generated workflow on GitHub Actions.

Added

  • /fnl-setup add checks reads a repository's package.json scripts, declared Python test runner and Makefile targets without running them, lists run: lines from its CI workflows as unverified candidates it never converts, proposes an ordered check list (a name and a JSON argument array each, never run through a shell by the plugin; known shells, launchers and inline-code forms are refused as a best-effort guard, not a sandbox; skipped items named) and, after a digest-bound yes, checks_setup.py saves it as that repository's entry in the host config's own ## Checks section (at most 20 checks of 1 KB each); ## Project settings is unchanged.
  • fnl-checks' checks.py run [--changed] [--base <ref>] runs a repository's stored checks in order through heavy_run.py and stops at the first failure (--changed narrows python -m unittest discover -s tests over a flat tests folder to one discovery per module select_tests.py names, and runs every other form and layout whole); an opt-in per-repository local-receipt mode lets a whole passing run on a clean, unmoved head stand in for missing or failing hosted checks in merge_check.py (only when the checkout's origin is the --repo repository, and the latest full run decides, one full run per repository at a time), which names it checks: local receipt (<head>); and checks_setup.py hook install|remove adds or removes an optional git pre-push hook that runs checks.py run --changed, refusing when core.hooksPath is set and never overwriting a different hook without a second flag.
  • checks_setup.py ci preview|apply writes, after a digest-bound yes, one new GitHub Actions workflow from a repository's stored checks: pull requests, pushes to the default branch, a weekly schedule, superseded runs cancelled, document-only changes skipped, caching for a known ecosystem. It refuses a link on the path and an Actions expression, keeps a backup, never overwrites without --replace-existing, and never commits or pushes; fnl-checks' references/ci.md describes it.
  • fnl-checks' checks.py usage --from <file> [--files-from <file>] [--limit-minutes N] summarises hosted CI runs from a gh run list --json file: run count, minutes rounded up per run, minutes per workflow and per event, the share spent on document-only changes and days left at the observed rate. It makes no network call and starts no process.
  • /fnl-update now goes on, after the host update, to a checklist from the new references/upgrades.json (one closed-schema entry per release, starting with 0.2.4) and offers each open setup step through fnl-setup with its own consent; /fnl-update whats-new only shows the checklist, and the session-start hook adds one read-only line naming /fnl-update while the installed version's notes are unseen.
  • update_check.py gains whats-new, onboard seen <version> and onboard skip <id> (the only writers of onboard.json: last_seen and skipped ids), target [<version>] [--evidence <file>] (latest by default; a chosen version only with matching gh release view evidence, an older one reported as a rollback with what is lost) and pin <version> / unpin, which silences the newer-release notice; the network check is unchanged. The Codex refresh procedure is now marked verified, and fnl-versioning asks the release pull request to write the upgrade-notes entry, which a test enforces.

Changed

  • fnl-verification is now fnl-checks, which also covers where a repository's checks run (locally or in CI); /fnl-verification keeps working as a user-only alias through 0.2.x.