2026-03-10 - 2026-09-10
Overview
1 Release published by 1 user
Published
v1
11 Pull requests merged by 1 user
Merged
#21 fix(prune): reclaim merged branches and size the volume for the clone
Merged
#18 fix(ci): trigger on edited so un-drafting actually lifts the draft skip
Merged
#16 fix(hardlink): name the mutable set directly, under both build-dir layouts
Merged
#15 fix(hardlink): content freshness moved switches, it was not withdrawn
Merged
#13 fix(cache): separate build directories for same-ref jobs, and a CI gate
Merged
#12 test(seed): pin reader_lock_acquire in hardlink_clone_into (#12)
Merged
#11 docs(cache): producer half of the depended-upon names contract
Merged
#9 test(seed): pin the two unguarded terms of the torn-clone condition
Merged
#8 docs(cache): write down the producer half of the leftover naming contract
Merged
#4 test(seed): force scenario 8's interleaving instead of racing for it
Merged
#2 fix(prune-cache): close the reader-marker check-then-delete window
9 Issues closed from 1 user
Closed
#20 bug(prune): merged-but-undeleted branches keep 40 G target dirs alive and min-free-percent never fires before the seed refuses
Closed
#17 A hardlink clone corrupts its source's linked executables: the linker writes through the shared inode
Closed
#14 unshare_mutable_paths collapses to a full copy under Cargo's build-dir layout v2 (stable 2026-11-12)
Closed
#10 hardlink_clone_into's reader_lock_acquire is unpinned: removing it leaves every suite green at the identical 129 assertions
Closed
#5 hardlink_clone_into's cp_rc guard is unpinned: removing it leaves every suite green
Closed
#6 publish-snapshot.sh:32 points at the wrong suite's scenario 8
Closed
#7 Document the producer half of the leftover naming contract with daniel/gitdan
Closed
#3 seed-target-dir-selftest scenario 8 is flaky: it asserts the rotation tore the clone, which is not guaranteed
Closed
#1 cargo-cache: eviction reader-check is check-then-delete, kept safe by policy rather than structure
12 Issues created by 1 user
Opened
#1 cargo-cache: eviction reader-check is check-then-delete, kept safe by policy rather than structure
Opened
#3 seed-target-dir-selftest scenario 8 is flaky: it asserts the rotation tore the clone, which is not guaranteed
Opened
#5 hardlink_clone_into's cp_rc guard is unpinned: removing it leaves every suite green
Opened
#6 publish-snapshot.sh:32 points at the wrong suite's scenario 8
Opened
#7 Document the producer half of the leftover naming contract with daniel/gitdan
Opened
#10 hardlink_clone_into's reader_lock_acquire is unpinned: removing it leaves every suite green at the identical 129 assertions
Opened
#14 unshare_mutable_paths collapses to a full copy under Cargo's build-dir layout v2 (stable 2026-11-12)
Opened
#17 A hardlink clone corrupts its source's linked executables: the linker writes through the shared inode
Opened
#19 Nothing asserts the CI workflow's own prohibitions: the edited trigger and both guard clauses are prose only
Opened
#20 bug(prune): merged-but-undeleted branches keep 40 G target dirs alive and min-free-percent never fires before the seed refuses
Opened
#22 Docs-drift catalog (standing): known stale documentation and comments
Opened
#23 feat(publish): sweep artifacts the lockfile no longer references before snapshotting — a dependency bump doubled zemyna's dev target