chore: Release axoasset version 0.6.1

[Gankra]

No description provided.

[ashleygwilliams]

curious: was this dynamically linking more than the one misty caught?

[Gankra]

per discussion in discord, #74 isn't actually fixing a "change", we've been happily linking lzma forever, so delaying the release on further discussion (my current stance is that since the dynamic link is so reliable, static linking can only come with downsides).

[mistydemeo]

per discussion in discord, #74 isn't actually fixing a "change", we've been happily linking lzma forever

It turns out this was only true on Intel: we were opportunistically linking it from the package manager, and because our Apple Silicon builds are on a runner without an Apple Silicon Homebrew, there wasn't a library for us to link against on Apple Silicon.

(my current stance is that since the dynamic link is so reliable, static linking can only come with downsides).

Since this is architecture-specific behaviour, and is also an artifact of our build environment, I think there is an upside here: predictability and intent. As well, since this liblzma comes from Homebrew, it means the Intel cargo-dist binary might not run for some of our users. If the user doesn't have Homebrew or doesn't have liblzma in a place the dynamic linker can find it, it won't run.