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: RELEASE.md
+6-3Lines changed: 6 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,8 +1,11 @@
1
1
# Releasing a new version of FSharpLint
2
2
3
-
1. Update the [changelog](CHANGELOG.md) since last release and get the changes onto master.
4
-
2. Tag the head of master with the version number in the format `vx.x.x` - for example: `v0.20.2`.
5
-
3. Push the tag to remote.
3
+
1. Update the [changelog](CHANGELOG.md) since last release: choose a version that increases the Major or Minor part of the version by 1, or the Revision
4
+
part of the version by 2, e.g.: `0.20.2` -> `0.23.0` or `0.20.2` -> `1.0` or `0.20.2` -> `0.20.4`, and add the entry (`## [X.Y.Z]`) summarizing all the
5
+
changes since the previous release (ideally one line per PR or commit).
6
+
2. Commit and push the change onto master branch, and wait until CI finishes successfully.
7
+
3. Tag the head of master with the version number in the format `vx.x.x` - e.g.: `git tag v0.20.4`.
8
+
4. Push the tag to remote: `git push origin vX.Y.Z` - this will start CI process that will create a GitHub release and publish the packages to NuGet.
6
9
7
10
After pushing the tag to remote, the publish pipeline will be kicked off which will:
0 commit comments