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
On every commit merged to `main`, the docs will automatically be rebuilt using DocFX, and then published using Github Pages as a "Deployment", similar to how the `StyraInc/opa-csharp` repo publishes its reference docs.
6
+
7
+
8
+
## Release workflows
9
+
10
+
### Minor changes
11
+
12
+
If you are doing minor bugfixes, simply merge your PRs to `main` after bumping the version in `src/Styra.Opa.AspNetCore/Styra.Opa.AspNetCore.csproj` (the main project file).
13
+
The release automation will then discover that the version differs from the latest version on NuGet, and will automatically publish the package after building and running tests.
14
+
15
+
16
+
### Major changes
17
+
18
+
If you are doing major changes, adding features, or fixing major bugs, do the same steps as mentioned above for the "Minor changes" workflow, but after merging, push up a release PR, and a tag, as detailed below.
19
+
20
+
Example:
21
+
- The `.csproj` file version is bumped from `0.2.42` to `0.3.0`.
22
+
- Create a git branch named `release-v0.3.0`.
23
+
- Add a `CHANGELOG.md` entry:
24
+
```md
25
+
## 0.3.0
26
+
27
+
My significant changes...
28
+
```
29
+
- Push up the branch to Github: `git push origin release-v0.3.0`
30
+
- Create a PR.
31
+
- After merging the PR, push up the tag `v0.3.0`, (e.g. `git checkout main && git pull && git tag v0.3.0 && git push origin v0.3.0`)
32
+
- Release automation will automatically pluck out the latest release notes, and use them as the body text for a Github Release.
0 commit comments