v0.8.12 Release

Thu, 22 Jan 2026 00:00:00 GMT

Today I’m publishing v0.8.12 of ZVM. I want to thank Vladimir Petrigo, Jack Parsons, and David James.

Vladimir is the latest in a long line of contributors to tackle the evergreen issue of linking files on Windows.

Unlike on Linux, creating symbolic links can be a restricted action that requires administrator permissions. In the past, to maintain behavior across operating systems, I had implemented a self-escalating process into ZVM to force ZVM to run as an administrator when necessary. I never knew how well it worked.

On my machine, it has never asked to escalate itself, and from the lack of issues I’ve gotten, I assumed it worked decently enough for everyone on Windows.

That was until a few weeks ago when I migrated ZVM’s linking code on Windows to use hard links. Hard links do not require admin permissions, but I heard they could still be fickle. I had no idea that they were useless in ZVM because it only links directories. Luckily, the symlink behavior was still in place as a backup. I come from a strong background in Linux and Unix systems. Sometimes I’m ignorant of features in Windows. Luckily, our community is full of smart, capable developers who are familiar with all kinds of systems. Vladimir nixed ZVM’s hard links and instead implemented junctions.

Junctions are like hard links, but they are for directories. As long as you’re pointing them to directories on the same volume, you’re good. That means—except for people who have customized their ZVM installation well beyond the defaults—this change should not affect anyone. If you are one of those people affected, please create an issue and let me know. I want everyone to have the flexibility to use ZVM however they please. It’s your computer, and I’m grateful you let a little bit of my code live on it.

I hope this is the end of linking issues on Windows. I know it probably won’t be, but for now, please create an issues if you experience problems on Windows.

Jack Parsons very kindly made a YouTube Short tutorial on how to install ZVM. I feel bad that I changed the website right after he published it, but every step he shows still works the same. Thank you Jack for using ZVM and for taking the time to be creative with my project. It means a lot.

David James kindly submitted an issue that brought attention to a design concern I had never thought of before. You can read more about it on GitHub.

Thank you. I want ZVM to be the best command line app you use. I want it to feel clean, feel fast, and feel well designed. I definitely know that there are warts. Some commands write through a logger. Others just print to stdout. Maybe some of the flags don’t make a ton of sense. I understand there is room to improve, and I will be making those improvements gradually this year.

I appreciate all feedback for ZVM. Design, feature, bug, etc. It doesn’t matter. I appreciate that people use my tool regularly and like it enough to leave a star.

If you have any questions, ideas, design thoughts, or just want to share something cool you made, please create an issue. I can be slow to get to them—I did get married this year, which took up a considerable amount of my bandwidth—but rest assured I am around and the project is fine. It has simply reached a stage of maturity where I don’t need to babysit it every day. It’s like my responsible teenage son who I trust not to burn the house down when I’m out, and who’ll use the $20 I left him to buy pizza instead of beer from his older friends.

Changelog v0.7.1

Mon, 27 May 2024 00:00:00 GMT

Hello, and welcome to the blog! This is the first Changelog posted to the website. Typically they’ll be short, mostly containing text from GitHub Releases, but with some of my additional thoughts and reasoning thrown in. Today ZVM enters its 0.7 series. This minor version cycle, I’ll be focusing on improving the foundations of ZVM in order to bring a hopefully exciting (and secret) feature in v0.8.

What changed?

Sync

The sync command has been retired as of ZVM v0.7.0. With v0.7.1, its functionality has been moved to the use command. Just run zvm use --sync to sync your local version of Zig with your project.

VMU

The --vmu flag has been upgraded to a command. It still works the same way, but now it’s just easier to access.

Upgrade

ZVM will now automatically check for upgrades after you’ve run a command. This just consists of a ping to ZVM’s GitHub repo using GitHub’s public API. Many tools including NPM and Deno do this automatically. If you would like to disable this functionality, you can set the new ZVM_SET_CU environment variable to anything. If you’d like to reenable it, just unset ZVM_SET_CU.

As always, if you have any questions, feedback, or want to help ZVM out, you can create an issue on our GitHub, or support free and open source software for less than the price of a cup of coffee on Polar.sh

zvm | Zig Version Manager | Blog

v0.8.12 Release

Changelog v0.7.1

What changed?

Sync

VMU

Upgrade