v1.2.0

verbatra/action now requires a verbatra config to exist exactly at the resolved working-directory before it runs a command. This is a breaking change from earlier releases.

What changed

• The action fails fast, before installing anything, if no recognized verbatra config is found directly inside working-directory. The check is strict: it never looks in a parent or ancestor directory, even if one holds a valid config.
• The failure names the exact resolved path that was checked and identifies the input that controls it (working-directory, and config-path when set explicitly).
• Once a config is found, the action always passes it to the CLI explicitly via --config <resolved-path>.

Versioning model change

Starting with this release, v1 is the single actively maintained tag for this action, updated continuously as fixes and features ship. The earlier v2 prerelease has been retired. Pin uses: verbatra/action@v1 (or a specific commit SHA for the security-conscious form, shown in the README).

Upgrading

If your config file lives only in a parent directory relative to working-directory (for example, a shared config at your repository root while working-directory points at a subdirectory), add a config file directly inside working-directory before upgrading, or the action will fail fast where it previously succeeded via inherited lookup.

See the README for full usage and the config discovery documentation for details.