I feel the need... the need... for speed!

The major change in this release is that action-validator now uses a list of files known to git when checking whether paths refer to files that actually exist.
This is good both because it is more correct (it won't false-positive on files that only exist in a local working copy), and also because it should greatly improve performance in large working copies.
Thanks to Antti Harju (@anttiharju) for this change.

We also provide a pre-built GitHub action now, so you can run action-validator in your own workflows with the simple snippet given in the README.
This exists also due to the efforts of Antti.

Free yourself from the shackles of the current working directory!

This release includes a new --rootdir command-line option, requested in #54, which allows you to specify a directory other than the current working directory from which to check that your glob patterns actually match something.
The validation schema has also been updated, to accept the latest supported version of the nodejs runtime in needs directives.

Excitingly, this release is the first that has been made possible (or at least, easier) through the generosity of kindly open source-loving people just like you!
A big shout-out goes to Andy, who contributed to my open source code fund to get the --rootdir feature implemented.
If you'd like to see your name up in lights, and help make more open source code exist, you can contribute too!

v0.7.0

Make the pre-commit config example more general

Actually allow 'attestations' in 'permissions'; WASM improvements

Tagged the wrong commit in the previous release, whoops.

Support+test negative globs

action-validator will now fail if a negative glob doesn't match any file paths in the repository.
Thanks to Kurtis Rainbolt-Greene (@krainboltgreene) for the initial implementation.

Loosen the requirements on runs-on

GitHub have finally admitted defeat in their attempts to keep any sort of structure to the runs-on directive, so we're following suit.
Thanks to Victor Sollerhed (@MPV) for the PR.

Updated schemas

Nothing big for this release, just an updated version of the schemas for workflows and actions that we use to validate whether the document is well-formed.

Binary releases for the correct architecture!

It turns out that if you don't tell Rust to build for a particular target, it... doesn't build for that target.
That meant that all those arm64 binaries we were building were actually x86_64 binaries.

Well now, hopefully, they're not.

Executable executables are good

This release is intended to fix a deficiency in the pre-commit support, so that the script referred to by the .pre-commit-hooks.yaml file is actually executable.

Remove wee_alloc from WASM builds

Turns out that wee_alloc is deprecated (or at least unsupported, per #33), and so it's better if we don't offer it as an option for WASM builds.
Apologies to the many, many people who no doubt have started using the WASM builds with wee_alloc already. 😁
Thanks to Ben Heidemann (@bcheidemann) for the PR (#37).

This release is also an attempt to provide something for pre-commit to grab a hold of, per #35.