Skip to content

Releases: mpalmer/action-validator

Free yourself from the shackles of the current working directory!

20 Aug 23:34

Choose a tag to compare

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

20 Aug 23:35

Choose a tag to compare

Make the pre-commit config example more general

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

09 Jul 23:00
a8e5e1a

Choose a tag to compare

Tagged the wrong commit in the previous release, whoops.

Support+test negative globs

23 Feb 05:51

Choose a tag to compare

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

24 Nov 20:52
d954e0d

Choose a tag to compare

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

11 Jul 04:16

Choose a tag to compare

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!

30 Jun 04:20

Choose a tag to compare

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

09 Mar 23:22

Choose a tag to compare

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

07 Mar 23:48
822d4cd

Choose a tag to compare

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.

wasm builds, multiple filenames, and binaries that support older distros

03 Mar 05:36

Choose a tag to compare

Three nice features in this release:

  1. The pre-built binaries now run on Linux distros that aren't at the bleeding edge of glibc, by linking against musl rather than glibc itself.
    Thanks to Matthieu Bizien (@MatthieuBizien) for the PR (#30).

  2. The CLI now accepts multiple files in one invocation.
    Thanks again to Matthieu Bizien (@MatthieuBizien) for the PR (#31).

  3. NPM packages containing a WASM build of action-validator, both an embeddable library and a CLI, are now available under the @action-validator NPM org.
    This support is a bit incomplete and I wouldn't go relying on it for critical purposes just yet, but having it in the tree is a good start towards to making it stable and full-featured.
    Great thanks to Ben Heidemann (@bcheidemann) for the fairly hefty PR (#26) and sticking to the roundabout of getting it to this point.
    Look for future improvements in this area.