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: docs/releases.md
+2-2
Original file line number
Diff line number
Diff line change
@@ -2,7 +2,7 @@
2
2
3
3
Pact Python is made available through both GitHub releases and PyPI. The GitHub releases also come with a summary of changes and contributions since the last release.
4
4
5
-
The entire process is automated through the [build](https://github.com/pact-foundation/pact-python/actions?query=workflow%3Abuild) GitHub Action. A description of the process is provided [below](#build-pipeline).
5
+
The entire process is automated through the [build](https://github.com/pact-foundation/pact-python/actions/workflows/build.yml?query=branch%3Amaster) GitHub Action. A description of the process is provided [below](#build-pipeline).
6
6
7
7
## Versioning
8
8
@@ -44,6 +44,6 @@ The publish step uses the `pypi` GitHub environment, and is gated behind a manua
44
44
- Generating a changelog based on the conventional commits since the latest release.
45
45
- Generating a new GitHub release with the changelog.
46
46
- Uploading the source distribution and wheels to PyPI.
47
-
- Creating a PR to update the `CHANGELOD.md` file with the new release notes.
47
+
- Creating a PR to update the `CHANGELOG.md` file with the new release notes.
48
48
49
49
While the generated changelog should be accurate, it may require some manual adjustments on the release page and in the PR.
0 commit comments