Repository navigation
Releases: ciatlas/flowpact
Releases · ciatlas/flowpact
Release list
v0.12.3
v0.12.2
v0.12.1
Immutable
release. Only release title and notes can be modified.
0.12.1 (2026-10-12)
Bug Fixes
- core:
always()is known to be true, so a condition like!always()is known never to run (#94) (7756e28) - core:
impact.publishlists each action once, findsaction.yamlin an exact directory, and treats./dirlikedir(#94) (7756e28) - core: a fractional array index is rounded down like GitHub, in expressions and matrix values (#94) (7756e28)
- core: a step's own
env:shadows the job's and the workflow's in that step's data flow (#94) (7756e28) - core: check names use GitHub's defaults for inputs without one, and are uncertain when a default is an expression (#94) (7756e28)
- core: files whose names start with
..are read, and locations before the start of a file are clamped (#94) (7756e28) - core: impact mode reads a base commit's linked files and directories like the working tree, bounded against loops and fan-out (#94) (7756e28)
- core: keys named like
constructorortoStringare not treated as defined, and no longer hide a file's schema errors (#94) (7756e28) - core: matrix include and exclude entries tell object values with different keys apart (#94) (7756e28)
- core: numbers convert to strings like GitHub (G15) in names,
format(),join()and comparisons (#94) (7756e28) - core: the hint for a missing base like
origin/mainsuggestsgit fetch origin main(#94) (7756e28) - core: the repository is detected from origin's url, not its pushurl (#94) (7756e28)
- core: walking the repository no longer loops on a directory linked into itself (#94) (7756e28)
v0.12.0
Immutable
release. Only release title and notes can be modified.
0.12.0 (2026-10-11)
⚠ BREAKING CHANGES
- flowpact moved to the ciatlas organization. Use
uses: ciatlas/flowpact@v0.12(GitHub redirects the old name). The docs and schemas are now at https://ciatlas.github.io/flowpact, and the old rumankazi.github.io/flowpact URLs no longer resolve. Contracts written by 0.11 or earlier name the old schema and docs URLs: runflowpact generateonce, orflowpact checkreports FP802. Releases up to 0.11.1 verify with--repo rumankazi/flowpact. See https://ciatlas.github.io/flowpact/docs/upgrading.
Features
- flowpact moves to ciatlas/flowpact and https://ciatlas.github.io/flowpact (#90) (634431c)
v0.11.1
v0.11.0
Immutable
release. Only release title and notes can be modified.
v0.10.1
Immutable
release. Only release title and notes can be modified.
0.10.1 (2026-10-10)
Bug Fixes
- action: name the plugin input's files that a run skips, and why (#82) (fd6c359)
- action: print no empty impact baseline group when impact mode does not run (#82) (fd6c359)
- action: warn when a copy of the action has an action.yml that cannot be read, instead of ignoring its defaults (#82) (fd6c359)
- cli: publish the npm package without devDependencies and scripts, so a vendored copy works in an npm workspace (#82) (fd6c359)
v0.10.0
Immutable
release. Only release title and notes can be modified.
0.10.0 (2026-10-10)
⚠ BREAKING CHANGES
- cli: The npm package's
dist/index.jsnow loads a second file next to it (code it shares with the new API), so a copy ofdist/index.jsalone no longer runs. Vendor the wholepackage/folder and runnode tools/flowpact/dist/index.js; see https://rumankazi.github.io/flowpact/docs/upgrading.
Features
- action: base-config and plugin inputs, so an organization's copy of the action carries its defaults and rules (#76) (442ff0b)
- cli: a programmatic API, one function per command, in the flowpact package (#78) (9fae33a)
Performance
v0.9.0
0.9.0 (2026-10-10)
⚠ BREAKING CHANGES
- Options now go after the command. Before 0.9, an option written before it (
flowpact --no-plugins lint) was silently dropped; it is now a usage error (exit 2). Writeflowpact lint --no-plugins;flowpact --helpandflowpact --versionwork as before. See https://rumankazi.github.io/flowpact/docs/upgrading.
Features
- cli: annotations, several reports in one run and plugin flags, for wrappers built on flowpact (#70) (a9e81cc)
- config: organization defaults with --base-config, and rules that are not loaded no longer stop a run (#73) (665f687)