Skip to content

0.4.0 - 2026-11-19

Latest

Choose a tag to compare

@github-actions github-actions released this 19 Nov 04:49

Release Notes

Added

  • rift A B on two directories compares the trees, as diff -r prints
    them: files only in one tree, a unified diff per changed file under a
    diff -r header, Binary files ... differ for files with a NUL in
    their first 8 KiB, and Renamed: for a file moved with its content
    unchanged. Symbolic links are compared by target and never followed.
    --summary lists one status per path and the counts. The whole run
    stays under --mem; one directory's listing must fit in a quarter of
    it, about 2 million entries at the default 256M, or the run is
    refused with a limit to rerun with.
  • rift --key --show-fields prints under each changed key the fields
    that differ, one per line: price: 10 -> 12. Fields are CSV
    columns named by the header (numbered for csv:N), top-level NDJSON
    members, or COPY columns. Values are cut at 64 bytes with ..., and
    (none) marks a field one record lacks.
  • --fields a,b compares only the named fields and implies
    --show-fields: a key whose other fields changed is not printed and
    does not count for the exit status.
  • rift-mcp has two tools for key mode. keyed_summary counts the keys
    added, removed and changed between two files and lists the first ten
    of each kind. keyed_changes returns a page of the changed keys with
    both records and, for a changed key, the fields that differ, a page at a
    time by an opaque cursor: one from another call, or after a file
    changed, is refused with a message to start again. A key from
    a pg_dump carries its COPY table as a table field. key takes
    the CLI's csv:NAME, csv:N, json:PATH and copy:NAME, and errors
    use the CLI's wording, a budget refusal ending in rerun with --mem.
    A keyed run counts its mem in the server's 512 MiB total and takes
    one of its four slots, but is not kept between calls: each page reruns
    the whole comparison, and a mem under about 260K to 400K, depending on
    the pair, is refused (caching is #89).
  • Each .deb, .vsix and .mcpb in a release has a <file>.sha256
    next to it, in the format of the archives' checksums: sha256.sum
    lists only the files dist builds (#69).
  • bench/compare.sh BASE HEAD SCRATCH builds two refs, runs them
    interleaved on fixed generated pairs, checks that their outputs match
    and prints the medians, spreads, peak heap and load as a table.

Changed

  • Output change: with --key copy:NAME, every key line names its table
    before the key, ~public.item:1 instead of ~1, in every output mode,
    so the same key in two tables no longer prints as the same line.
    Scripts that parse COPY key lines must strip the new prefix. A colon
    in the table name prints as \:. Duplicate-key errors name the table
    too: duplicate keys: public.item:7. CSV and NDJSON output is
    unchanged. In rift-core, KeyedChange gains a table field and
    KeyError::Duplicate lists TableKey values.
  • A directory given with a file is refused with give two files or two directories (exit 2) instead of not a regular file.
  • rift serve waits up to 5 seconds for room, at most four calls at a
    time, before it answers busy, but only for a client that declares
    capabilities.retry_after in initialize. Other clients keep the
    immediate busy answer. initialize ignores a capability it does not
    know and refuses a known one of the wrong type.

Fixed

  • --key csv: on a file whose last record leaves a quote open and that
    ends in a lone CR reported that record as changed against the same
    file without the CR, and kept the line breaks in the key when the
    quote was in the key column. The final CR now counts as a line break,
    as it does outside quotes, and such files compare equal.
  • Key mode gave its threads' memory back to the budget before the
    threads had exited, so a few KiB they allocated on the way out counted
    against no reservation, and under rift serve or the MCP server
    against the next comparison. It now waits for them. With --key copy:
    the first table name could also take 80 bytes more than reserved.
  • On a file with duplicate keys, rift --key could stop with a
    rerun with --mem refusal instead of the duplicate-key error, when a
    pass that met the duplicates ended with its share of --mem full.

rift-diff 0.4.0

Install rift-diff 0.4.0

Install prebuilt binaries via shell script

curl --proto '=https' --tlsv1.2 -LsSf https://github.com/rubtsov-stan/rift/releases/download/v0.4.0/rift-diff-installer.sh | sh

Download rift-diff 0.4.0

File Platform Checksum
rift-diff-aarch64-apple-darwin.tar.xz Apple Silicon macOS checksum
rift-diff-x86_64-apple-darwin.tar.xz Intel macOS checksum
rift-diff-aarch64-unknown-linux-gnu.tar.xz ARM64 Linux checksum
rift-diff-x86_64-unknown-linux-gnu.tar.xz x64 Linux checksum

Verifying GitHub Artifact Attestations

The artifacts in this release have attestations generated with GitHub Artifact Attestations. These can be verified by using the GitHub CLI:

gh attestation verify <file-path of downloaded artifact> --repo rubtsov-stan/rift

You can also download the attestation from GitHub and verify against that directly:

gh attestation verify <file-path of downloaded artifact> --bundle <file-path of downloaded attestation> --repo rubtsov-stan/rift

rift-mcp 0.4.0

Install rift-mcp 0.4.0

Install prebuilt binaries via shell script

curl --proto '=https' --tlsv1.2 -LsSf https://github.com/rubtsov-stan/rift/releases/download/v0.4.0/rift-mcp-installer.sh | sh

Download rift-mcp 0.4.0

File Platform Checksum
rift-mcp-aarch64-apple-darwin.tar.xz Apple Silicon macOS checksum
rift-mcp-x86_64-apple-darwin.tar.xz Intel macOS checksum
rift-mcp-aarch64-unknown-linux-gnu.tar.xz ARM64 Linux checksum
rift-mcp-x86_64-unknown-linux-gnu.tar.xz x64 Linux checksum

Verifying GitHub Artifact Attestations

The artifacts in this release have attestations generated with GitHub Artifact Attestations. These can be verified by using the GitHub CLI:

gh attestation verify <file-path of downloaded artifact> --repo rubtsov-stan/rift

You can also download the attestation from GitHub and verify against that directly:

gh attestation verify <file-path of downloaded artifact> --bundle <file-path of downloaded attestation> --repo rubtsov-stan/rift