v0.2.3

• Fixed the code to detect whether the filename includes a version number that looks like an extension. If the filename ended with the version, like foo-1.2.3, then this was not handled properly. It only worked if there something after the version as well, like foo-1.2.3-linux-amd64. Based on a bug report by @FelisNivalis. GH #77.

v0.2.2

• Added an is_musl method to the UbiBuilder struct to allow setting this manually.
• Fix handling of file "extensions" that just contain the OS and architecture, like ".linux.amd64". Implemented by @jdx (Jeff Dickey). GH #71.

v0.2.1

• When running on Linux, ubi now checks to see if the platform is using musl and will prefer a release artifact with "musl" in the name. Previously, it would usually pick a glibc artifact if there were multiple artifacts that matched the platform OS and architecture, which would not work on musl-based platforms like Alpine Linux. Reported by @burner. GH #70.
• Fixed a bug in the handling of release artifact names with version numbers in them that look like extensions. This caused ubi to fail when trying to install shfmt 3.10.0, and probably many other tools. Reported by @jimeh (Jim Myhrberg). GH #67.
• Work around release artifacts that put the platform name after a period, so it looks like an extension. This is the case with direnv, at least with the v2.35.0 release, which has releast artifacts like "direnv.linux-amd64". Reported by @jimeh (Jim Myhrberg). GH #67.

v0.1.1

• Fix documentation links to link to the library docs, not the CLI docs.

v0.1.0

• UBI can now be used as a library. See the ubi docs on docs.rs for more details.

v0.0.32

• Fix support for plain .tar files with no compression.
• Fix handling of files with a version in the filename and no extension, like shfmt_v3.8.0_linux_arm64. This was fixed before but I broke it in the 0.0.31 release.

v0.0.31

• Added support for the .bz2 and .tar.bz2 file extensions.

v0.0.30

• When a project's releases contain a mix of file names with and without an architecture, ubi will try one of the no-architecture names if it doesn't find any matches for the current architecture. An example of this is the yt-dlp/yt-dlp project, which has releases named yt-dlp_linux and yt-dlp_linux_aarch64.
• ubi is now always compiled with rustls, instead of using openssl on some platforms.

v0.0.29

• If there is only one match for the platform's OS and the release filename has no architecture in it, ubi will now pick that one (and hope that it works). This fixes an issue reported by @krisan. GH #48.
• As of this release there are no longer binaries built for MIPS on Linux. These targets have been demoted to tier 3 support by the Rust compiler.

v0.0.28

• Fixed a bug with tarballs that use the GNU sparse format. Such tarballs were not extracted properly, leading to the extracted executable being garbled. This was an issue with the macOS x86-64 release of ubi, which broke the --self-upgrade flag on that platform. Reported by Olaf Alders. GH #45.