Repository navigation
lexlean 0.4.3
lexlean 0.4.3
language 1.0
compiler-semantics 4bd46ef62ba56a77cb3c6453346671a809ccd665fc1f5334e4b1b9dce01f3245
lean-toolchain leanprover/lean4:v4.32.2
Container image (GitHub Packages):
docker pull ghcr.io/uor-foundation/lexlean:0.4.3@sha256:85bc117eeb9293ef6bd0cbe8638b32061e4bcbde06dff06f5ee1429e00593934
The image carries the compiler and leanprover/lean4:v4.32.2, so lexlean verify runs in it.
lexlean-0.4.3-binaries.tar.gz holds one binary per supported
host (SPEC.md §8.3) under bin/<target>/.
checksums.txt covers every attached file and each binary inside the
tarball, so verify after extracting it:
tar -xzf lexlean-0.4.3-binaries.tar.gz
sha256sum -c checksums.txt
The digests:
fbf32f6843b7cfc70943d46e4eef7c55e42e69ffbe8573cdfb3de18a01dba829 CONFORMANCE.md
bbb4fbcc6a39c1c62bb655638b2c47f4f5b3d1623192d3d551a84690bf866a21 ERRORS.md
62c7a1e35f56406896d7aa7ca52d0cc0d272ac022b5d2796e7d6905db8a3636a LICENSE-APACHE
b65b82603a4875244eaecc241d1666217ae7d9f8bf4ad3e7b1ac88d8888126ee LICENSE-MIT
b1cae511d10ebd7e0bf6632d165fde6c23f491d6d780ccb29d8a02b37e386247 MANIFEST.sha256
e843767b5442280c4c40a96819445f3a67c2e39db6625a68e2ee109a1142ea83 SPEC.md
2bb6363948f28bdb03d8dffac7628481bfa535e7ec0f642b1648e28450364dd2 bin/aarch64-apple-darwin/lexlean
387e5c4ba802c3530650b8fbd2c0cb70aebe7bbc7721d55416b141aae101dc72 bin/aarch64-unknown-linux-gnu/lexlean
eedb586e2843a61baa02f063ec1e8aa4fc12cfb127c31f6a2f6409be5bd37afd bin/x86_64-apple-darwin/lexlean
7cd5e8f842740ed22f7132ae9eba2c4c9601032086a762c64d68834547d8bbee bin/x86_64-pc-windows-msvc/lexlean.exe
e3e6472307385d2c2980db23aee188027e91a7090c4f5593fc64dc2418ddf5a1 bin/x86_64-unknown-linux-gnu/lexlean
5ec52b9fb9364997340b1cd07e6323bf7363317cc1decda0e9c3b1475008f28e compiler-semantics-id.txt
8c8b800802efe691f018cbcb88a490a6619e058b6db1e079f744b2b7dcd67925 lexlean-0.4.3-binaries.tar.gz
51b094a3b30cac06e15e05018a5f475125560cfdbe3373c00d7232e611c15dc1 lexlean.crate
0e6981fdcec1e2956a0227c92d51f9cd2d28acab333c174818a185d575c7422a release-check.txt
34446b384e4a5c7d6f3797fb8a7513b8a993e37de6f63bdb0024a21bc26bcff7 release-identity.json
6590bfeb693529e992f21979b252ccee2136bc4e8b7d20b9d06167c6936c1dd2 sbom.json
77f82fde053c743a98075438b8d46c42a48b2917add722d6c9a57cd129d36bc1 version-output.txt
dedc67c612b7b842a6be31ca18646e3fde6fe9d26b873194869b086128e0858c vv-evidence.txt
release-check.txt records what SPEC.md §30 refuses at this version.
§2.3 fixes 1.0.0 as the first release satisfying the complete
specification, so this tag does not claim that criterion; the report names
each part of it that does not hold. See CHANGELOG.md.