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
+19Lines changed: 19 additions & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -44,3 +44,22 @@ If there is already a stable version with the same version number as in `pyproje
44
44
so don't forget to update the version number before releasing a new version.
45
45
The release process also fails when the released version is not described in `CHANGELOG.md`,
46
46
so don't forget to describe the changes in the new version there.
47
+
48
+
### Beta release checklist
49
+
50
+
Beta release happens automatically after you merge a pull request or add a direct commit to the master branch. Before you do that check the following:
51
+
52
+
- Make sure that in the [pyproject.toml](https://github.com/apify/apify-sdk-python/blob/master/pyproject.toml) a project version is set to the latest non-published version.
53
+
- Describe your changes to the [CHANGELOG.md](https://github.com/apify/apify-sdk-python/blob/master/CHANGELOG.md) in the section with the latest non-published version.
54
+
55
+
### Production release checklist
56
+
57
+
Production release happens after the GitHub release is created. Before you do that check the following:
58
+
59
+
- Make sure that the beta release with the latest commit is successfully deployed.
60
+
- Make sure that all the changes that happened from the last production release are described in the [CHANGELOG.md](https://github.com/apify/apify-sdk-python/blob/master/CHANGELOG.md).
61
+
- When drafting a new GitHub release:
62
+
- Create a new tag in the format of `v1.2.3` targeting the master branch.
63
+
- Fill in the release title in the format of `1.2.3`.
64
+
- Copy the changes from the [CHANGELOG.md](https://github.com/apify/apify-sdk-python/blob/master/CHANGELOG.md) and paste them into the release description.
0 commit comments