Skip to content

Commit 7aa2d7a

Browse files
committed
Update RELEASE.md instructions to use GitHub release links.
1 parent 3961c96 commit 7aa2d7a

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

RELEASE.md

+3-3
Original file line numberDiff line numberDiff line change
@@ -8,10 +8,10 @@ When a new Zig version is released, the process is as follows:
88
* Commit the change.
99
* Tag a release with
1010
`git tag v$(ZigVersion).$(ToolsetVersion) -m v$(ZigVersion).$(ToolsetVersion) -s`
11-
(e.g. `v0.8.0.1`).
11+
(e.g. `v0.13.0.1`).
1212
* 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).
13+
* Edit the draft release on GitHub to add a link to the Zig release, such as
14+
[this one](https://github.com/ziglang/zig/releases/tag/0.13.0).
1515
* Publish the release on GitHub.
1616

1717
Fresh NuGet packages will then be built and published by an automatic workflow.

0 commit comments

Comments
 (0)