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: CONTRIBUTING.md
+2-2Lines changed: 2 additions & 2 deletions
Original file line number
Diff line number
Diff line change
@@ -130,11 +130,11 @@ make run-doc
130
130
Publishing new versions to [PyPI](https://pypi.org/project/apify_client) is automated through GitHub Actions.
131
131
132
132
-**Beta releases**: On each commit to the master branch, a new beta release is automatically published. The version number is determined based on the latest release and conventional commits. The beta version suffix is incremented by 1 from the last beta release on PyPI.
133
-
-**Stable releases**: A stable version release may be created by triggering the `run_release` GitHub Actions workflow. The version number is determined based on the latest release and conventional commits (`auto` release type), or it may be overriden using the `custom` release type.
133
+
-**Stable releases**: A stable version release may be created by triggering the `release` GitHub Actions workflow. The version number is determined based on the latest release and conventional commits (`auto` release type), or it may be overriden using the `custom` release type.
134
134
135
135
### Publishing to PyPI manually
136
136
137
-
1.**Do not do this unless absolutely necessary.** In all conceivable scenarios, you should use the `run_release` workflow instead.
137
+
1.**Do not do this unless absolutely necessary.** In all conceivable scenarios, you should use the `release` workflow instead.
0 commit comments