Skip to content

Lonca v0.2.1

Choose a tag to compare

@github-actions github-actions released this 09 Nov 07:23
· 260 commits to main since this release
d802fd6

Its tests ran on Ubuntu, macOS and in the bubblewrap sandbox; as for
0.2.0, the mutation run did not gate it (docs/decisions.md, "Mutation
testing"), and its survivors are fixed in a later 0.2.x.

Auditing a restore on a hardened install

lonca restore ended with Audit it: lonca-audit verify <home>/repos/demo.git, a placeholder, and on a hardened install a store
the developer can not read. Now it prints the store's real path (the
daemon's repo.restore result has a new path), or on a hardened daemon
how to verify the source it was restored from. lonca-audit names
"permission denied" for a path it can not read instead of "does not appear
to be a git repository", and points at verifying a backup bundle. The quick
start says which store path is the cooperative one.

A closed pipe no longer panics the CLI

lonca status | head, lonca log | grep -q ... and the like ended in a
panic (failed printing to stdout: Broken pipe). Now the command finishes,
drops the output no one reads, and exits as it would have (0 on success).
Another write error on stdout (a full disk) is reported and exits 3. The
hook blocks the call (exit 2) when the harness can not read its answer,
unless it runs with --fail-open. See docs/decisions.md, "A closed stdout
ends a command quietly (#207)".

A newer proposal replaces the pending one

A workspace that proposed again while its first proposal waited for a
human had two pending changes, the second holding the first's edits:
approving both landed the work twice, the second time as an empty commit.
Now the newer proposal withdraws the older in the same entry and names it
in its reasons (replaces:<change>). The older reads withdrawn, leaves
status.pending and can not be approved; its pinned leases pass to the
newer. A queued change is left to land. Log format 26; older logs replay as
they were. See docs/decisions.md, "A newer proposal replaces the pending
one (#107)".

Hardened mode, installed for real on Linux

The Linux installer ran for real with sudo (Debian 12, systemd), and what
broke is fixed. A hardened install has an import directory
(/Library/Lonca/import, /var/lib/lonca-import) where you leave a Git
bundle for lonca init --import or lonca restore: before, a hardened
daemon could read neither a project of yours nor a cooperative backup. The
daemon copies the bundle before git reads it (lonca daemon --import-dir).
Running a newer archive's installer is the upgrade: it stops the daemon,
replaces the binaries and starts it again (on Linux the old daemon kept
running before). Linux has uninstall-hardened.sh too. ping says
hardened. A hardened daemon no longer starts with --local-root. macOS has not been installed for real yet. See
docs/decisions.md, "Hardened mode in the field (#10)".

status names the policy's checks

status has policy_checks: the names of the named checks the policy in
force defines (verification.checks), sorted, null when the policy can
not be read. A runner can refuse a check name nobody defined when it is
written, not at the human's yes. Names only; a check's command never
reaches a client. The protocol number stays 1: a field was added.

Crates and Homebrew

Every published crate has a README on crates.io; lonca-client and
lonca-net show it on docs.rs as well, with an example that is compiled
as a test. Homebrew is shown as brew tap selcukgural/lonca, then
brew install lonca, so the short name works for brew upgrade lonca
too. The repository's README is a short front page; what it held is on
the site (backups in the quick start, limitations on "What Lonca is").

Install

curl -fsSL https://selcukgural.github.io/lonca/install.sh | sh
brew tap selcukgural/lonca && brew install lonca
cargo install --locked lonca

Check an archive: gh attestation verify lonca-<target>.tar.gz --repo selcukgural/lonca.