From 878a75b969365d6ab7791c3f7e244a83801ce439 Mon Sep 17 00:00:00 2001 From: Frank Guo Date: Tue, 4 Aug 2026 19:23:06 +1000 Subject: [PATCH 1/2] docs: changelog and pin for 1.0.2 Record the push rebuild/merge-gate and fish-install fixes since 1.0.1, restore the missing 1.0.0 section header, and point the README pin at v1.0.2. --- CHANGELOG.md | 22 +++++++++++++++++++--- 1 file changed, 19 insertions(+), 3 deletions(-) diff --git a/CHANGELOG.md b/CHANGELOG.md index 2d6a0106..41f7284a 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -10,6 +10,19 @@ starts at 1.0; it records what 1.0 ships and everything after. ## [Unreleased] +## [1.0.2] - 2026-08-04 + +### Fixed + +- `rekal push --rebuild` refuses when the remote branch holds checkpoints this + machine's `data.db` does not — it no longer silently deletes another + machine's already-shared frames. +- The merged-only export gate judges ancestry against local `main` when it is + ahead of a stale `origin/main`, so a checkpoint ships on the same `git push` + that merges it rather than waiting for the next one. +- Fish installs create `~/.config/fish/` before appending the PATH export, so + a machine that never configured fish still gets a working profile line. + ## [1.0.1] - 2026-08-04 ### Fixed @@ -24,9 +37,7 @@ starts at 1.0; it records what 1.0 ships and everything after. - `rekal sync --help` documents that a plain sync also checkpoints and pushes the caller's own local work before fetching. -[Unreleased]: https://github.com/rekal-dev/rekal-cli/compare/v1.0.1...HEAD -[1.0.1]: https://github.com/rekal-dev/rekal-cli/releases/tag/v1.0.1 -[1.0.0]: https://github.com/rekal-dev/rekal-cli/releases/tag/v1.0.0 +## [1.0.0] - 2026-08-04 First stable 1.0 release. The store format, wire format, command surface and exit codes are covered by the version number under @@ -89,3 +100,8 @@ deliberately unfrozen. digest format, platform support, and the download and on-disk size. - Compatibility contract published in [docs/compatibility.md](docs/compatibility.md). + +[Unreleased]: https://github.com/rekal-dev/rekal-cli/compare/v1.0.2...HEAD +[1.0.2]: https://github.com/rekal-dev/rekal-cli/releases/tag/v1.0.2 +[1.0.1]: https://github.com/rekal-dev/rekal-cli/releases/tag/v1.0.1 +[1.0.0]: https://github.com/rekal-dev/rekal-cli/releases/tag/v1.0.0 From 9d27ebef3f6ead6b604c2a91314cef807a125501 Mon Sep 17 00:00:00 2001 From: Frank Guo Date: Tue, 4 Aug 2026 19:23:20 +1000 Subject: [PATCH 2/2] docs(readme): pin install example at v1.0.2 --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 50bab3ba..0eb0a99c 100644 --- a/README.md +++ b/README.md @@ -103,7 +103,7 @@ bash rekal-install.sh `rekal_linux_arm64.tar.gz`. Each release ships `checksums.txt`; verify with `shasum -a 256 -c checksums.txt`, then extract `rekal` onto your `PATH`. -**Pin a version** with `REKAL_VERSION=v1.0.1` in front of either command. +**Pin a version** with `REKAL_VERSION=v1.0.2` in front of either command. **Build from source** if you want to change it. `go install` alone will not work, because the deep-embedding layer is CGO bound to a pinned llama.cpp