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
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.
6
+
7
+
After pushing the tag to remote, the publish pipeline will be kicked off which will:
8
+
* Build the package
9
+
* Create a github release
10
+
* Pushes the package to NuGet
11
+
* Publishes the docs to github pages
12
+
13
+
## Dependencies
14
+
15
+
* Github secret: `NUGET_KEY`.
16
+
* This is the API key from nuget, used to push the package to nuget.
17
+
* At the moment the key lives under `duckmatt`'s nuget account, but I believe the `fsprojects` account should also be able to create an applicable API key.
0 commit comments