SECTION 11 / DISTRIBUTION
Releases & licenses
Release channels
| Channel | Artifact |
|---|---|
| crates.io | lanyard-ssh-agent source package |
| GitHub Releases | x86_64 and aarch64 Linux archives plus checksums |
| Nix flake | package, app, checks, and Home Manager module |
| GitHub Pages | This versioned operator manual |
Versioning
Every main revision must pass the full repository check before the release state machine can start. Release-plz then derives changelog entries and versions from Conventional Commits, and the trunk-based workflow signs the release commit and tag. Cargo-dist builds platform artifacts from that exact tag commit. Third-party actions are pinned to immutable revisions so changes to the release machinery are reviewable.
Publication order
- Build and checksum both Linux archives.
- Upload the verified files to a draft GitHub Release.
- Publish the matching source package to crates.io.
- Make the GitHub Release public only after the registry confirms the version.
No release pull request or second release workflow is involved. Safe retries reuse the draft and the existing signed tag; inconsistent state fails closed. Rapid pushes can coalesce into one natural release, but unverified code is never substituted for the revision that passed.
Verify a download
sha256sum --check lanyard-ssh-agent-*.sha256Dual license
Unless explicitly stated otherwise, Lanyard is available under either the Apache License, Version 2.0 or the MIT license, at your option. Contributions are accepted under the same terms.