Repository navigation
v0.1.4
v0.1.4
Release preflight alignment for read-only GitHub Actions GITHUB_TOKEN
execution inside registry-publish.yml. The library, language bindings,
conformance corpus and canon command are unchanged from 0.1.3.
What it ships
- Rust crates
canonprims-coreandcanonprims-json(crates.io). - Go module
github.com/3leaps/canonprims(packagecanon), standard
library only and cgo-free. canoncommand for linux amd64/arm64, darwin arm64 and windows
amd64/arm64.- Python package
canonprims(PyPI): an abi3 wheel per platform for
CPython 3.10 and later, on linux amd64/arm64 (manylinux2014, glibc 2.17 or
later), darwin arm64 and windows amd64/arm64. No source distribution. - npm package
@3leaps/canonprims: one WebAssembly module with no
imports, embedded in an ES module with no runtime dependencies. Tested on
Node.js 20 and 22.
The wheels and the npm package are release assets: built and tested in the
tag workflow, listed in both checksum manifests and covered by both
signatures. The packages on PyPI and npm are these exact files.
Release machinery
scripts/release-github-preflight.sh: when invoked under GitHub Actions
(GITHUB_ACTIONS=true) with acontents: readGITHUB_TOKEN(which has no
Administrationscope), accepts the redactedbypass_actors: nullfield on
GET /repos/3leaps/canonprims/rulesets/<id>while verifying all other ruleset
fields, and verifies release immutability on the published release object
(GET /repos/3leaps/canonprims/releases/tags/vX.Y.Z,.immutable == true)
when/immutable-releasesreturns HTTP 403. Maintainer preflight outside
GitHub Actions continues to require both the explicitOrganizationAdmin
bypass_actorsarray and/immutable-releases.docs/releases/v0.1.3.md: records the runner group (default) and runner
image versions for the two unversioned arm64 cells of thev0.1.3release
workflow run.
Conformance
- Corpus
conformance/canonical-json/v0, 180 cases, unchanged.
MANIFEST.jsonsha256:
de3ac543580ddb90f7e3a6e72239097274d3635ea783f302a9260b5a7d0c8d90. - Rust and Go agree byte for byte on the corpus and on generated input:
crosscheck seeds20261022and20261023, 5000 inputs each, on every
native CI cell. - Each binding runs the whole corpus against its installed package (the
wheel, or the packed npm tarball), and its corpus results and its output on
the same crosscheck seeds equal Rust's byte for byte.
Verification
canon canonicalizes and digests; it verifies no signatures, so it embeds no
key. To verify this release, check the signed tag v0.1.4 and the signed
checksum manifests against the public pins committed in the tagged commit
(docs/security/); see docs/security/README.md. A wheel or the npm tarball
downloaded from PyPI or npm has the SHA-256 listed for it in SHA256SUMS.