Johnathan Corgan 8cda39b21f Check the crate would publish on every maint push, and publish it at a release tag ...

The crate is published to crates.io as fips-mesh from v0.5.3. A new Crate
workflow runs testing/check-crate.sh on every maint push and v* tag. The
script checks the package name and, on a tag, that the version matches it.
It checks the keyword and category rules crates.io enforces only at upload,
runs `cargo publish --dry-run --locked`, checks the size limit, and runs the
library's unit tests from the unpacked .crate. Nothing is uploaded.

At a release tag, and not at a pre-release one such as v0.5.3-rc1, a
publish job runs after the check, in the crates-io environment that holds
the registry token and waits for approval. master and next are left out for
now: their root package depends on the unpublished fips-core by path, which
crates.io refuses.

2026-10-16 15:45:40 +00:00

..

scripts

Pin every GitHub Action to a commit SHA, and verify the nak download

2026-08-11 15:44:07 +00:00

workflows

Check the crate would publish on every maint push, and publish it at a release tag

2026-10-16 15:45:40 +00:00