Repository navigation
Aardvark v0.2.1
Aardvark v0.2.1
This release publishes aardvark-core 0.2.1 with a library-first API for staging the pinned Aardvark Pyodide distribution from host setup tooling.
Highlights
- Adds
aardvark_core::pyodide_distribution::stage_pyodide_distribution(...)behind the opt-inpyodide-stagingfeature. - Keeps staging-only dependencies out of default
aardvark-coreconsumers. - Refactors
aardvark-cli assets stageto reuse the shared core staging implementation. - Keeps
assets verifyclear for manifests that do not record feature metadata. - Ensures docs.rs builds include the new
pyodide-stagingAPI surface.
Version Pins
- Aardvark: 0.2.1
- Pyodide: 0.29.4
- V8/rusty_v8 crate: 149.2.0
- Rust MSRV: 1.96
Host Packaging Notes
- Hosts that need to prepare runtime assets programmatically can depend on
aardvark-core = { version = "=0.2.1", features = ["pyodide-staging"] }in setup/build tooling. - Normal runtime consumers can keep
aardvark-corewithout default features; the staging dependencies remain opt-in. - The CLI remains a workspace/debugging tool and is not published to crates.io.
Pyodide Distribution Assets
The GitHub release includes staged Aardvark Pyodide distributions:
aardvark-0.2.1-pyodide-v0.29.4-core.tar.gz- distribution fingerprint:
sha256:b829959a79b2a094823423b52f5a4d3c01876f856216d98d385173844524d594 - archive SHA-256:
ca2241749eae03503f10e9f6fe0020208e13cad794b0a95259293728df2d8267
- distribution fingerprint:
aardvark-0.2.1-pyodide-v0.29.4-full.tar.gz- distribution fingerprint:
sha256:c687ada5f575576c4e3d5bd59173ac7cfd7fc74fcb65201278948f466cbf343f - archive SHA-256:
cc286c63d159816d561307c80ef505814d5bc05f60290747c965ca4f35ae1977
- distribution fingerprint:
Limitations
- Aardvark is still experimental; public APIs, manifests, and runtime semantics may change.
- Windows builds are not supported or tested.
- JavaScript bundles must be self-contained; Aardvark does not resolve npm packages or
node_modules. - Filesystem quota enforcement currently covers the
/sessiontree. - Streaming outputs and incremental logs are not available; handlers return one payload.