the install page names v0.4.21 now that it is fetchable: RELEASE_TAG moves only after the release reached R2, which is what the pin means and why it is a land of its own. v0.4.21 published 3 of 5 triples, windows x64 and both linux, with the two darwin triples carried forward on v0.4.14 in the signed manifest platform_pins, and the detector passed 3 of 3 on an anonymous curl of the hero one-liner: it installed v0.4.21 through all four surfaces, the PATH edit resolved in a fresh login shell and loot --version printed exactly loot 0.4.21. verified by DOWNLOADING rather than by trusting the upload: the windows zip and the linux tarball each match their own .sha256 and the aggregate sha256.sum, and the unpacked windows binary reports 0.4.21. the forge and the relay already answer /info with 0.4.21 on format 14. the site suite is green (659 passed and 61 skipped over 60 files) with release-pin rule 3 now satisfied, the build and the byte budget are green, and no ceiling moves (#2089) e5e701df · dbf3dbe6…
Renames are not followed. loot's tree maps a path to an address, so a rename is a delete and an add. This list is the history of the name, not of the bytes.