Home

• Get the latest version from ziglang.org/download (zigup master && zig version works)
• Inside the zig repo, run git checkout SHA -b next-release

Notes on reviewing commits for a release

Run the following command to save commit logs to a file in chronological order:

git log --stat --reverse OLD_SHA..NEW_SHA > changes

--stat adds the "files changed" summary

Open that file and go through the commit messages to see what's broken. Document that for the release notes. Maybe there's a better commit to release other than the latest.

Submitting binaries for Bazel Mirror

Binaries are only available from ziglang.org temporarily. Bazel provides more permanent storage so we can use them to store the zig binaries. Here's how to submit them:

• Open https://github.com/bazelbuild/bazel/issues/new/choose
• Select "Mirror request"
• Title the issue "zig VERSION" for consistency
• Enter URLs, like in https://github.com/bazelbuild/bazel/issues/17635
• Wait a "business hour" (AFAIK someone oncall at Google gets a low-urgency notification) for the artifacts to be mirrored

Getting the list of commits:

# add --reverse to get the commits in chronological order
git rev-list --reverse OLD_SHA..NEW_SHA 

Get a full diff between revisions and check for changes to "pub things".

git diff OLD_SHA..NEW_SHA | rg pub

for rev in $(git rev-list --reverse OLD_SHA..NEW_SHA); do echo $rev && gitk $rev; done