5 Commits

Include renames

Author	SHA1	Message	Date
claude@clouddev1	bd5be5ecc7	fix(ci): read release version from Cargo.toml, not cargo metadata (ADR-0054) ... The ADR-0054 version guard piped `nix develop -c cargo metadata` to node, but the flake devShell prints a banner to stdout — corrupting the JSON pipe, so the guard aborted under `set -e` and the v0.2.0 release failed there (before building anything). Replace it with a toolchain-free `grep -m1 '^version = ' Cargo.toml` (the anchor excludes dependency `version =` keys). No real version mismatch occurred — the tagged commit has version 0.2.0.	2026-06-17 21:58:32 +00:00
claude@clouddev1	c30a6114b9	feat(cli): --version/-V + in-app version command + release guard (ADR-0054) ... Cargo.toml version is the single source of truth, surfaced by a --version/-V CLI flag and an in-app `version` command (both via cli::version_text -> cli.version_line). release.yaml gains a guard that fails the release unless the v* tag equals v<CARGO_PKG_VERSION>, keeping --version, the release name, and the asset in lockstep. New app command wired across grammar/REGISTRY/dispatch/usage/help/hint-corpus/keys; 6 test-first tests. Also fixes a stale "macOS deferred" comment in release.yaml. ADR-0054 + README index + plan-doc step 1.	2026-06-16 15:57:54 +00:00
claude@clouddev1	298475b326	ci: D1 release matrix over the four non-macOS targets ... release.yaml becomes test (once, host) -> build (matrix) over the four cargo-zigbuild targets; each matrix job uploads its binary + .sha256 to the shared release (idempotent create-or-get). Records the expansion in ADR-ci-001 (2026-06-13 amendment); macOS stays deferred.	2026-06-13 12:14:49 +00:00
claude@clouddev1	89b9392c25	ci: release job — test before publish, pin bash, fix diagnostic ... - Run cargo test before the build so a tag never publishes untested code. - Pin shell: bash on the scripted steps; the runner defaults to dash, which rejected `set -o pipefail` and failed run 22's package step. - Swap `file` (absent in the slim image) for `ls -l`.	2026-06-12 22:11:24 +00:00
claude@clouddev1	88145225cc	ci: release workflow — static binary to Gitea releases on tag ... On a v* tag, builds the x86_64-unknown-linux-musl binary in the CI image and publishes it (+ .sha256) to a Gitea release via the API and the auto GITEA_TOKEN. x86_64 Linux only for now; rest of the D1 matrix and D3 packaging layer on later. Correctness comes from the branch gate.	2026-06-12 21:43:23 +00:00