Repository navigation
Releases
Releases · ut-issl/inka
v0.0.5
Immutable
release. Only release title and notes can be modified.
This release changes nothing in inka itself and fixes how the release workflow publishes the crates.
Distribution
- The crates are published to crates.io, which v0.0.4 failed to do, so
cargo install inka-cliembeds the viewer. - A dry run of the release workflow rehearses the crates.io publish with
cargo publish --dry-run.
v0.0.4
Immutable
release. Only release title and notes can be modified.
This release builds the graph viewer into inka, so inka serve works without downloading anything else.
Command line (inka)
inka serveserves the graph viewer compiled into the binary, so--assetsis no longer needed.--assets <DIR>still serves a viewer bundle from disk, for working on the viewer itself.cargo install inka-cliembeds the viewer as well.
Distribution
- The web viewer bundle
inka-web-<version>.tar.gzis no longer attached to the GitHub Release. - The npm package is staged on npm by the release workflow and made public when a maintainer approves it.
v0.0.3
Immutable
release. Only release title and notes can be modified.
This release changes nothing in inka itself and fixes how the release workflow publishes the packages.
Distribution
- The npm package
@inka-project/inka-evidenceis published to npm, which v0.0.2 failed to do. - Publishing to Open VSX fails at once when the
OVSX_PATsecret is missing, instead of waiting for a token.
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.
v0.0.1
Immutable
release. Only release title and notes can be modified.
The first release of inka, a text DSL for writing design arguments as structured, reviewable claims.
Every package in the repository is released together under this version.
Command line (inka)
inka checkloads a project and reports every structural problem in its argument.inka evalevaluates the argument: whether it is currently valid, and if not, why not.inka reviewlists the approval targets, walks them interactively, or records a single decision.inka fmtrewrites every argument file in the canonical layout;--checkonly lists the files it would change.inka exportwrites the argument as cytoscapeelementsJSON, andinka serveserves the read-only graph viewer.
Editor support
inka-lspprovides diagnostics, hover, go to definition, find references, rename, and semantic tokens.- It also provides inlay hints, approval code lenses, and document formatting.
- A VS Code extension in
editors/vscoderegisters the language and starts the server.
Test evidence
- Test evidence v1 is a JSON schema for the results of test runs that an argument can cite.
inka-evidence-rustemits it from cargo-nextest runs.- The
inka-evidencePython package emits it, with a pytest plugin. - The
@ut-issl/inka-evidencenpm package emits it, with a Vitest adapter.
The packages are not yet published to crates.io, PyPI, npm, or the VS Code Marketplace.
Build them from this repository.