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
Copy file name to clipboardExpand all lines: ReleaseChecklist.md
+7-7Lines changed: 7 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -127,13 +127,13 @@ At least a day before the release:
127
127
## Prerelease
128
128
-[ ] Check that all tests on the latest commit on `develop` or `breaking` branch (whichever was chosen for the prerelease) are green.
129
129
-[ ] Create a [release on GitHub](https://github.com/argotorg/solidity/releases/new).
130
-
- Set the target to the `develop` or `breaking` branch and the tag to the new version with a prerelease suffix, e.g. `v0.8.5-pre.6`.
131
-
Version matches the next release (`develop`) or the next breaking release (`breaking`).
132
-
The prerelease number in the suffix is 1-based, sequential, resets after a full release and is counted separately for `develop` and `breaking`.
133
-
- Include the following warning: `**The release is still in progress. You may see broken links and binaries may not yet be available from all sources.**`.
134
-
- Include the current, incomplete changelog.
135
-
- Check the `Set as a pre-release` box.
136
-
- Click the `Publish release` button on the release page, creating the tag.
130
+
- Set the target to the `develop` or `breaking` branch and the tag to the new version with a prerelease suffix, e.g. `v0.8.5-pre.6`.
131
+
Version matches the next release (`develop`) or the next breaking release (`breaking`).
132
+
The prerelease number in the suffix is 1-based, sequential, resets after a full release and is counted separately for `develop` and `breaking`.
133
+
- Include the following warning: `**The release is still in progress. You may see broken links and binaries may not yet be available from all sources.**`.
134
+
- Include the current, incomplete changelog.
135
+
- Check the `Set as a pre-release` box.
136
+
- Click the `Publish release` button on the release page, creating the tag.
137
137
-[ ] Wait for the CI runs on the tag itself.
138
138
-[ ] Switch to the tag that archives have to be created for.
139
139
-[ ] Create the `prerelease.txt` file: `scripts/prerelease_suffix.sh pre "$(git describe --tags --exact-match)" > prerelease.txt`.
0 commit comments