Skip to content

Releases: tristanisham/zvm

v0.8.5

22 Jan 20:43
Compare
Choose a tag to compare

What's Changed

New Contributors

Full Changelog: v0.8.4...v0.8.5

v0.8.4

10 Jan 17:48
Compare
Choose a tag to compare

Full Changelog: v0.8.3...v0.8.4

Fixed #101

v0.8.3

10 Jan 17:09
Compare
Choose a tag to compare

What's Changed

  • fix: typo by @gh-liu in #111
  • add loongarch64 by @candicandi in #109
  • add powerpc64le
  • ZVM now supports linux/ppc64le and linux/loong64 platforms. Please report any bugs in these builds of ZVM if you use them as there currently isn't a test suite for this platforms.

New Contributors

Full Changelog: v0.8.2...v0.8.3

v0.8.2

04 Dec 00:16
Compare
Choose a tag to compare

What's Changed

  • list only sub folders as installed versions (ignoring any other files) by @profelis in #106

This solves an issue on MacOS where zvm ls would print .DS_store files. Basically,

New Contributors

Full Changelog: v0.8.1...v0.8.2

v0.8.1

14 Nov 18:11
Compare
Choose a tag to compare

Full Changelog: v0.8.0...v0.8.1

Oops, forgot to look for a .exe extension on Windows 😳

v0.8.0

14 Nov 17:50
Compare
Choose a tag to compare

What's Changed

New Contributors

Full Changelog: v0.7.9...v0.8.0

Run installed version of Zig without switching your default

If you want to run a version of Zig without setting it as your default, the new run command is your friend.

zig version
# 0.13.0

zvm run 0.11.0 version
# 0.11.0

zig version
# 0.13.0

This can be helpful if you want to test your project on a newer version of Zig without having to switch between bins, or on alternative flavor of Zig.

How to use with alternative VMUs

Make sure you switch your VMU before using run.

zvm vmu zig mach
run mach-latest version
# 0.14.0-dev.1911+3bf89f55c

If you would like to run the currently set Zig, please keep using the standard zig command.

v0.7.9

28 Oct 19:35
Compare
Choose a tag to compare

Full Changelog: v0.7.8...v0.7.9

v0.7.8

28 Oct 14:48
Compare
Choose a tag to compare

HOTFIX

This release provides a hotfix for a bug introduced in v0.7.7 when trying to install ZLS on master.

Problem: ZVM v0.7.7 may have saved an invalid 'zlsVersionMapUrl' to your settings,
which causes this error. The latest version, v0.7.8, can fix this issue by using the correct URL.

To resolve this:

  1. Open your ZVM settings file: '~/.zvm/settings.json'
  2. Remove the 'zlsVersionMapUrl' key & value from the file (if present).

What happens next: ZVM will automatically use the correct version map the next time you run it
If the issue persists, please double-check your settings and try again, or create a GitHub Issue.

Full Changelog: v0.7.7...v0.7.8

v0.7.7

25 Oct 02:29
Compare
Choose a tag to compare

What's Changed

  • Use ZLS release worker for selecting builds by @no-realm in #102

New Contributors

Full Changelog: v0.7.6...v0.7.7

Updated Version Map Setting

Set Version Map Source

ZVM lets choose your vendor for Zig and ZLS. This is great if your company hosts it's own internal fork of Zig, you prefer a different flavor of the language, like Mach.

zvm vmu zig "https://machengine.org/zig/index.json" # Change the source ZVM pulls Zig release information from.

zvm vmu zls https://validurl.local/vmu.json
                                       # ZVM only supports schemas that match the offical version map schema. 
                                       # Run `vmu default` to reset your version map.

zvm vmu zig default # Resets back to default Zig releases.
zvm vmu zig mach # Sets ZVM to pull from Mach nominated Zig.

zvm vmu zls default # Resets back to default ZLS releases.

You can now use zvm list --vmu to see set version maps

v0.7.6

27 Sep 19:33
Compare
Choose a tag to compare

What's Changed

Force Install

  • Install zig and zls only if version is not already installed by @timodempwolf in #100
  • Added alwaysForceInstall field to settings.json to enable old force behavior

As of v0.7.6 ZVM will now skip downloading a version if it is already installed. You can always force an install with the --force or -f flag.

zvm i --force master

You can also enable the old behavior by setting the new alwaysForceInstall field to true in
~/.zvm/settings.json.

New Contributors

Full Changelog: v0.7.5...v0.7.6