Heimdall v0.1.2
Changes
Highlights
- Publish the official daemonless Heimdall CLI through PyPI for x86_64 and
aarch64 Linux across glibc and musl systems. - Keep PyPI packaging local and immutable: each wheel embeds one verified
release binary and performs no install-time download or build. - Publish the exact checksum-verified GitHub Release wheels through PyPI OIDC
with no registry token or second release command.
Added
- Add the public
heimdall-egressPyPI distribution withheimdalland
heimdall-egressconsole commands, Python 3.9+ metadata,pipx.runsupport,
and project-owned install, architecture, mode, and security documentation. - Add native wheel acceptance for metadata rendering, checksums, x86_64
installation and execution, bundled-path discovery, static linkage, and
aarch64 architecture integrity.
Changed
- Extend
just release-githubto build and verify the two PyPI wheels locally,
attach them and their checksums to the GitHub Release, and let the thin
publish-pypi.ymlworkflow upload only those immutable assets with pinned
uvand GitHub OIDC. - Document persistent and ephemeral installation through
uv,pip, and
pipx, including the stable native-path authorization boundary required by
real proxy sessions.
Known limitations
- Native macOS support is not available yet.
- Native aarch64 real-eBPF VM acceptance remains future work; the aarch64 wheel
is checked for architecture, static linkage, metadata, and checksum integrity.
Install
Download the archive and matching SHA-256 file for your Linux architecture.
Follow the versioned installation guide
for checksum verification, setup authorization, upgrade, and rollback.
Release artifacts
heimdall-egress-0.1.2-x86_64-linux-musl.tar.gzheimdall-egress-0.1.2-aarch64-linux-musl.tar.gzheimdall-egress-0.1.2.tgzfor npm trusted publishing- x86_64 and aarch64
heimdall_egress-0.1.2-*.whlfiles for PyPI
trusted publishing - One SHA-256 file beside each archive
Verification
The release host completed the authoritative local source checks, current and
Linux 6.6 LTS real-eBPF VM suites sequentially, and native, npm, and PyPI
package gates before the tag or assets were published.