|
|
@@ -12,15 +12,17 @@
|
|
|
- Make sure the copyright year in args.ml has the correct value
|
|
|
- Update `version` in `haxe.opam`
|
|
|
- Check if the protocolVersion in displayJson.ml has to be updated
|
|
|
-- Make an empty GitHub release in https://github.com/HaxeFoundation/haxe/releases (do this first because we need the tag for the builds)
|
|
|
-- Wait for the CI to build (check https://build.haxe.org/builds/haxe/)
|
|
|
-- Get https://github.com/simn/hxgithub
|
|
|
-- Store your GitHub personal access token in .github-token
|
|
|
-- Run something like this: `neko release.n -h 4.0.0-rc.1 -u -uw -ur -d haxe_2019-02-01_development_1fdd3d5.zip --dry`
|
|
|
-- Tell yourself that you're gonna fix `-doc` generation next time
|
|
|
-- Write the announcement to `./haxe-version/RELEASE.md`
|
|
|
-- If everything was working, run the command again without `--dry` (and probably without the `-d`)
|
|
|
+- Create a version tag and push it with above changes (CI needs to run on the tag)
|
|
|
+- Make an empty GitHub release in https://github.com/HaxeFoundation/haxe/releases
|
|
|
+- Wait for the CI to build (check https://build.haxe.org/builds/haxe/, look for `haxe_[date]_refs/tags`)
|
|
|
+- Get https://github.com/HaxeFoundation/hxgithub
|
|
|
+- Follow "Haxe releases" section of hxgithub README, with the equivalent of `-d haxe_2023-04-28_refs/tags/4.3.1_964c84c.tar.gz`
|
|
|
+ - Tell yourself that you're gonna fix `-doc` generation next time
|
|
|
+ - Make sure changelog isn't empty in `./haxe-version/CHANGES.md`
|
|
|
+ - Write the announcement to `./haxe-version/RELEASE.md`
|
|
|
+ - If everything was working, run the command again without `--dry`
|
|
|
- Update https://github.com/HaxeFoundation/haxe.org/blob/staging/downloads/versions.json
|
|
|
+- Wait for staging to update, check everything related to release and merge to master
|
|
|
|
|
|
# Cleanup
|
|
|
|
Rudy Ges