Repository navigation
Releases: absolutejs/bvm
Release list
bvm v0.1.5
BVM now accepts AbsoluteJS Bun builds labeled with SemVer build metadata, such as 1.4.3+absolute.2, while continuing to support existing -absolute.N release tags and installations.
- Preserves exact release labels for installation, selection, and downloads.
- Handles URL-encoded metadata in GitHub's latest-release redirects.
- Matches engine ranges against the upstream Bun version.
- Continues forwarding Bun's own version output unchanged. Newly built patched Bun binaries will embed their label; existing Bun binaries are unchanged.
Validated with unit tests, Clippy, and end-to-end checks on Linux, macOS, and Windows, plus static Linux checks.
All six platform binaries are listed in SHASUMS256.txt, signed with the AbsoluteJS release key (SHASUMS256.txt.sig, Ed25519). bvm self update and the install scripts verify that signature.
bvm v0.1.4
bvm 0.1.4
Every binary is listed in SHASUMS256.txt, signed with the AbsoluteJS release key (SHASUMS256.txt.sig, Ed25519).
bvm self update and the install scripts check that signature before running anything.
bvm v0.1.3
bvm 0.1.3
Every binary is listed in SHASUMS256.txt, signed with the AbsoluteJS release key (SHASUMS256.txt.sig, Ed25519).
bvm self update and the install scripts check that signature before running anything.
bvm v0.1.2
bvm 0.1.2
Every binary is listed in SHASUMS256.txt, signed with the AbsoluteJS release key (SHASUMS256.txt.sig, Ed25519).
bvm self update and the install scripts check that signature before running anything.
bvm v0.1.1
bvm 0.1.1
Every binary is listed in SHASUMS256.txt, signed with the AbsoluteJS release key (SHASUMS256.txt.sig, Ed25519).
bvm self update and the install scripts check that signature before running anything.
bvm v0.1.0
bvm 0.1.0
Every binary is listed in SHASUMS256.txt, signed with the AbsoluteJS release key (SHASUMS256.txt.sig, Ed25519).
bvm self update and the install scripts check that signature before running anything.