Skip to content

docs: changelog and pin for 1.0.2 #87

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
rekal-dev merged 2 commits into from
Aug 4, 2026
Merged

docs: changelog and pin for 1.0.2 #87

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
878a75b
docs: changelog and pin for 1.0.2
Aug 4, 2026
9d27ebe
docs(readme): pin install example at v1.0.2
Aug 4, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
22 changes: 19 additions & 3 deletions CHANGELOG.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand All @@ -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
Expand Down Expand Up @@ -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
2 changes: 1 addition & 1 deletion README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand Down
Loading