Repository navigation
v0.0.2
Immutable
release. Only release title and notes can be modified.
This release adds inka init and is the first to publish the packages to their registries.
Command line (inka)
inka init [PATH]scaffolds a new project withinka.toml, an emptyvalues.toml, and a starter argument.- The new project passes
inka checkandinka fmt --checkas it stands. - The project name defaults to the directory's name, and
--nameoverrides it. --phasessetsphases.order, and its first entry becomesphases.current(M0by default).inka initonly adds files and never overwrites an existing project.
Distribution
- GitHub Releases now attach prebuilt binaries for Linux (musl) and macOS on x86_64 and aarch64, and Windows on x86_64.
- They also attach the VS Code extension per platform, the Python wheels and sdist, and the npm package.
- The web viewer bundle for
inka serve --assetsis attached as well. - Every asset has a build provenance attestation and is listed in
SHA256SUMS. - The crates are published to crates.io,
inka-evidenceto PyPI, and@inka-project/inka-evidenceto npm. - The VS Code extension is published as
inka-project.inka-vscodeto the VS Code Marketplace and Open VSX. - The VS Code extension bundles
inka-lsp, and uses it before one onPATH.
Breaking changes
- The npm package is renamed from
@ut-issl/inka-evidenceto@inka-project/inka-evidence.