How closely will the releases on Homebrew track Github?

[igbanam]

I came back to reading the docs after being out for a while. I see things like v env and v tool and get excited about it. But my compiler doesn't have these.

$ v tool
v: unknown command `tool`.
Did you mean `build-tools`?
Run  v help  for usage.

Turns out Homebrew's tip is at V 0.5.2, but there's another tag of sorts from 2 weeks ago.

When can we expect a version bump?

[DahanItamar]

Homebrew tracks only V's numbered releases, not the weekly tags. So it won't move until there's a release after 0.5.2, and I can't tell you when that will be. Only the V maintainers know.

Why Homebrew is behind

• The vlang formula builds from refs/tags/0.5.2.tar.gz. Its livecheck regex is ^v?(\d+(?:\.\d+)+)$, which matches only numeric tags like 0.5.2.
• The tag you saw from two weeks ago is weekly.2026.41 (October 5). It's a weekly snapshot, so Homebrew's update check never considers it.
• The latest numbered release is still 0.5.2, from July 12.
• v tool and v env are newer than that: cmd/tools/vtool.v and cmd/tools/venv.v are on master but not in the 0.5.2 tag. The current docs describe master, which is why you see commands your compiler doesn't have.

Getting them now

Build from source, as described in the README:

brew uninstall vlang   # the formula and a symlinked source build would both install `v`
git clone --depth=1 https://github.com/vlang/v
cd v
make
./v symlink            # puts `v` on your PATH

After that, v up updates the clone in place, so you get changes as they land on master instead of waiting for a Homebrew bump.

Don't run v up on the Homebrew install itself. It expects a git checkout, and in a directory without .git it runs git init and git reset --hard origin/master there. Homebrew manages that directory, so keep the two installs separate. If you'd rather stay on Homebrew, the next numbered V release should come through the formula's normal update process.