k-dash

k-dash implements the frozen v1 design in docs/design/: content-addressed TVM-FFI CUDA kernel builds, direct OCI Distribution API access, an atomic local cache, Docker/Nix AOT builds, and synchronous Python loading.

The runnable example is examples/axpy. It exports an AXPY CUDA kernel as one TVM-FFI kernel.so and includes an AFS/H20 smoke test.

python -m pip install -e '.[test]'
pytest
k-dash --help

The public Python API is intentionally one function:

import k_dash

module = k_dash.load("examples/axpy", version="1", jit_args={"block_size": 256})

Source ignore patterns are relative to the project root. Directory patterns such as build, build/, and build/** exclude the whole subtree without walking it. Existing file globs remain supported; required source files cannot be excluded. Symbolic links are not packaged or traversed.

In an already isolated CI container without a Docker daemon, k-dash publish --backend nix ... builds AOT artifacts directly with installed Nix. This explicit backend disables Nix's nested sandbox and build-user group; the CI container must provide isolation. It uses the same frozen release source, locked dependencies, BuildSpec and binary validation as Docker AOT. Docker remains the default. Registry credentials are not forwarded to the Nix build subprocess environment.

Releasing to PyPI

Package versions come from git describe through hatch-vcs. An exact tag such as v0.1.0 builds version 0.1.0; commits after a tag receive a development version. Build from a Git checkout with its tags available.

Before the first release, configure a PyPI Trusted Publisher for project k-dash (use a pending publisher if the project does not yet exist):

• GitHub owner: reyoung
• Repository: k-dash
• Workflow: publish.yml
• Environment: pypi

The workflow uses OIDC, so no PyPI API token secret is required. Push a release commit and its annotated tag to build, validate, and publish the wheel:

git tag -a v0.1.0 -m "Release v0.1.0"
git push origin HEAD
git push origin v0.1.0

The workflow retains the built wheel as a GitHub Actions artifact and publishes it only after its metadata and version match the release tag.