これは旧バージョンです。最新版は0.13.0です。 ubi 0.13.0 · リリース日:
インストーラーファイル 0.8.4
| アーキテクチャ | 種類 | インストール範囲 | ファイルサイズ | ダウンロード | SHA256 |
|---|---|---|---|---|---|
| 64ビット | ZIP → ポータブル | — | — | github.com | VirusTotal |
| ARM64 | ZIP → ポータブル | — | — | github.com | VirusTotal |
| 32ビット | ZIP → ポータブル | — | — | github.com | VirusTotal |
リンクとSHA256はWindows Package Managerのコミュニティマニフェストから取得しています。実行する前に、ダウンロードしたファイルのハッシュを照合してください。
リリースノート
- This is the same as 0.8.3, but I had to publish this with a new tag because of a failed experiment with using GitHub's new immutable releases feature.
- Fixed a bug where ubi would pick an asset with 64 in the name when trying to pick the best match on a 64-bit platform. This could include things like project-Linux-1.64.0.tgz, where the 64 is part of the version. Now it uses a pickier regex that looks for actual CPU architecture names, like x86-64 or arm64.
- Made it possible to use ubi on Android.
- Added linuxstatic as a string to look for when checking for Linux asset names. Apparently, the yao tool produces assets with this string in the name (why the hate for dashes, I ask?). Reported by @egnor (Daniel Egnor). GH #142.
- Improved libc matching. Previously, this only checked for literal substrings like -gnu or -musl. This meant that an asset name with dashes, like foo_linux_musl.tar.gz, would not be matched. Now this uses regexes to better match the libc name. Reported by @egnor (Daniel Egnor). GH #142.
- When on a platform with musl as its libc, ubi will now prefer an asset with an explicit indication that it was compiled with musl over an asset with no libc indication in the name. In other words, it will prefer project-linux-x86-64-musl.tar.gz over project-linux-x86-64.tar.gz. Suggested by @egnor (Daniel Egnor). GH #142.
