Repository navigation
0.3.1 - 2026-11-09
Release Notes
Added
rift --key --show-recordsprints the records under each change: A's
behind-, B's behind+, with the prefix on each line of a
record that spans lines. Rift reads the records back from the files
through a 64 KiB buffer taken from the--membudget.--statsprints the peak heap after an error as well, and
rift git-diff --statsprints it after the diff or the error.
Changed
--memandrift git-diff --memare at least 64K. Below that, parsing
the command line alone took more heap than the limit. The reserve
leaves key mode less room at a small--mem, so it takes more passes:
at 1M a 128 MiB CSV pair takes 145 passes instead of 122 and runs about
19% longer.- With the reserve below, a run that only just fit a small limit can now
stop with a budget error.--summaryof a 32 MiB SQL dump at
--mem 1Mdid on 8 threads. Thererun with --mem Nit prints names a
limit that gets past that point; here 1089K, which gives the same
summary as before. - An approximate hunk says why in plain words: the unified diff writes
@@ ... @@ approx: <reason>,--statscounts the segments for each
reason, the terminal view shows the reason in the status line when it
fits, andrift-mcpadds it to the hunk header.Hunk::approxin
rift-coreis now anOption<ApproxReason>.
Fixed
- Key mode at a small
--mempeaked up to 10 KiB over the limit: its
output buffers and other heap outside the budget went uncounted, and in
the other modes so did the thread pool's heap. Rift now keeps 48 KiB
plus 12 KiB per pool thread (one per core, orRAYON_NUM_THREADS) of
--memout of the budget for that heap, and
rerun with --mem Nadds it to its advice. - Output closed early, as in
rift a b | head, no longer prints an error.
Rift exits 141 without a message, the status a shell reports for
diffkilled by SIGPIPE. rift git-diffexits 0 without a message when git's pager quits early,
sogit diffno longer reports "external diff died".- A failed write to standard output says "write failed", not "read failed".
- Two files, or two regions, that share no line are no longer marked
approx. Deleting one side and inserting the other is the smallest
diff there, and Rift now proves it from the line hashes: a different
hash means a different line. The script is the same as before. --summaryno longer prints anapproxline. It refines nothing, so
its count was always 0 whatever the files.- The
summaryofrift serveandrift-mcpcountedapproxsegments
by the map, which never marks one, so it read 0.approxnow counts
the refined segments that came out approximate, anddiffersthe other
differing segments; together they are still every differing segment.
rift-mcpaddsrefined_segments; inrift serve,progress.doneis
that count.
Known issues
- Key mode at exactly
--mem 16Mruns on one thread: the reserve takes
the refine half just under the 8 MiB key mode needs for several. On a
128 MiB CSV pair it takes 2.21 s instead of 1.25 s in 0.3.0, about 77%
longer.--mem 16528Kor more restores the old time. - Key mode's line order can differ between runs once it uses several
threads. The set of lines is always the same.
rift-diff 0.3.1
Install rift-diff 0.3.1
Install prebuilt binaries via shell script
curl --proto '=https' --tlsv1.2 -LsSf https://github.com/rubtsov-stan/rift/releases/download/v0.3.1/rift-diff-installer.sh | shDownload rift-diff 0.3.1
| 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/riftYou 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/riftrift-mcp 0.3.1
Install rift-mcp 0.3.1
Install prebuilt binaries via shell script
curl --proto '=https' --tlsv1.2 -LsSf https://github.com/rubtsov-stan/rift/releases/download/v0.3.1/rift-mcp-installer.sh | shDownload rift-mcp 0.3.1
| 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/riftYou 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