You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Periodically we nominate a new Zig nightly version to be the version that Mach targets, and begin the meticulous process of updating every Mach project to use that new version.
This is the tracking issue to do that for the next scheduled nomination (see the date in the issue title.)
You may have been linked to this issue because you sent a pull request to update a Mach project to use a new Zig API - if that is the case we do appreciate the PR and will look at merging it once this process begins. In the meantime, your PR may stay open for a while. You can either use a fork of the project, or use the version of Zig that Mach currently supports.
Update process
It is time to begin (see date in issue title, we aim to begin this checklist between the 1st-4th of that month.)
In machengine.org repository static/zig folder, wrench script nominate-zig-index-update nominate 2024.1.0-mach-wip has been ran and the index.json has been updated.
#wrench automation (!wrench schedule-now update-zig-version) has created new pull requests to update the Zig version used in CI of all our projects, and it matches index.json.
The Nomination history has a new section for the latest nightly Zig version which Wrench used in its PRs, with a warning at the top **IN-PROGRESS:** This version is currently being nominated, see [the tracking issue](https://github.com/hexops/mach/issues/1135) for details. Once everything looks good, the new Zig version is confirmed to be working with Mach, we will declare success, close the issue, and remove this in-progress warning..
#mach-dev Discord message: Beginning the process of nominating a new Zig version; $GITHUB_ISSUE
#wrench automation (!wrench script-all install-zig) has updated the Zig version used by self-hosted GitHub actions runners.
"First-order projects" below (which have zero build.zig.zon dependencies) have been updated, their CI is passing/green using the new version.
"Second-order projects" below (which have build.zig.zon dependencies) have been updated, their CI is passing/green using the new version.
In machengine.org repository static/zig folder, wrench script nominate-zig-index-update finalize 2024.1.0-mach-wip has been ran and the index.json has had -wip removed and the mach-latest entry has been updated.
The **IN-PROGRESS** warning in the Nomination history has been removed.
A new issue has been filed for the next nomination.
A #progress announcement has been made:
We've just finalized nominating and updating to Zig 2024.1.0-mach. We encourage you to update your projects to that Zig version now. :)
I dont know exactly how this works, but would not be nice if the version matches with https://ziglang.org/download/index.json hopefully zig releases will become more "stable"?
as with zigup right now
../zigup/zig-out/bin/zigup 0.13.0-dev.351+64ef45eb0
install directory '/Users/devworks/zig'
mkdir '/Users/devworks/zig'
rm -rf '/Users/devworks/zig/0.13.0-dev.351+64ef45eb0.installing'
mkdir '/Users/devworks/zig/0.13.0-dev.351+64ef45eb0.installing'
downloading 'https://ziglang.org/builds/zig-macos-aarch64-0.13.0-dev.351+64ef45eb0.tar.xz' to '/Users/devworks/zig/0.13.0-dev.351+64ef45eb0.installing/zig-macos-aarch64-0.13.0-dev.351+64ef45eb0.tar.xz'
error: download 'https://ziglang.org/builds/zig-macos-aarch64-0.13.0-dev.351+64ef45eb0.tar.xz' failed: HTTP server replied with unsuccessful response '404 Not Found'
rm -rf '/Users/devworks/zig/0.13.0-dev.351+64ef45eb0.installing'
But also signatures are gone from zig I believe...
ziglang.org purges nightly builds after some time, the pkg.machengine.org mirror hosts our nominated versions (binaries for every os/arch, and the signatures) forever.
Periodically we nominate a new Zig nightly version to be the version that Mach targets, and begin the meticulous process of updating every Mach project to use that new version.
This is the tracking issue to do that for the next scheduled nomination (see the date in the issue title.)
You may have been linked to this issue because you sent a pull request to update a Mach project to use a new Zig API - if that is the case we do appreciate the PR and will look at merging it once this process begins. In the meantime, your PR may stay open for a while. You can either use a fork of the project, or use the version of Zig that Mach currently supports.
Update process
machengine.org
repositorystatic/zig
folder,wrench script nominate-zig-index-update nominate 2024.1.0-mach-wip
has been ran and theindex.json
has been updated.!wrench schedule-now update-zig-version
) has created new pull requests to update the Zig version used in CI of all our projects, and it matches index.json.**IN-PROGRESS:** This version is currently being nominated, see [the tracking issue](https://github.com/hexops/mach/issues/1135) for details. Once everything looks good, the new Zig version is confirmed to be working with Mach, we will declare success, close the issue, and remove this in-progress warning.
.Beginning the process of nominating a new Zig version; $GITHUB_ISSUE
!wrench script-all install-zig
) has updated the Zig version used by self-hosted GitHub actions runners..zigversion
file https://github.com/hexops/mach/blob/main/.zigversion has been updated.machengine.org
repositorystatic/zig
folder,wrench script nominate-zig-index-update finalize 2024.1.0-mach-wip
has been ran and theindex.json
has had-wip
removed and themach-latest
entry has been updated.**IN-PROGRESS**
warning in the Nomination history has been removed.First-order projects
These projects have zero
build.zig.zon
dependencies, we update them first - and in any order.Second-order projects
These projects have dependencies on other projects. We update them in the exact order below, top-to-bottom.
The text was updated successfully, but these errors were encountered: