We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
1 parent 3961c96 commit 7aa2d7aCopy full SHA for 7aa2d7a
RELEASE.md
@@ -8,10 +8,10 @@ When a new Zig version is released, the process is as follows:
8
* Commit the change.
9
* Tag a release with
10
`git tag v$(ZigVersion).$(ToolsetVersion) -m v$(ZigVersion).$(ToolsetVersion) -s`
11
- (e.g. `v0.8.0.1`).
+ (e.g. `v0.13.0.1`).
12
* Push the commit and the tag.
13
-* Edit the draft release on GitHub to add a release notes link, such as
14
- [this one](https://ziglang.org/download/0.8.0/release-notes.html).
+* Edit the draft release on GitHub to add a link to the Zig release, such as
+ [this one](https://github.com/ziglang/zig/releases/tag/0.13.0).
15
* Publish the release on GitHub.
16
17
Fresh NuGet packages will then be built and published by an automatic workflow.
0 commit comments