Hm, arguably that was a bugfix because:

          If set to `true`, Nix falls back to building from source if a
          binary substitute fails. This is equivalent to the `--fallback`
          flag. The default is `false`.

So fallback flag shouldn't have bailed out at all.

Release notes could use some love indeed though.

Did some benchmarking of tarball unpacking on my sluggish macos opencore x86 hackintosh:

current master with multithreaded sink:

37.32s user 1.36s system 360% cpu 10.731 total

2.33:

38.60s user 0.56s system 156% cpu 25.064 total

2.32:

42.26s user 14.93s system 104% cpu 54.691 total

2.22 (just to see how bad loose objects really are)

15.11s user 71.89s system 75% cpu 1:55.67 total

Very nice. The system time reduction is very nice on top of the general parallel hashing of blobs. Much more efficient and faster too.

In reply to @shine:proqqul.net
why do workflows require approval to run? is that a new thing?