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
``get_tasks_count()`` method returns the number of tasks with the given optional parameters for: ``project_name``, ``batch_name``, ``type``, ``status``,
Copy file name to clipboardExpand all lines: docs/pypi_update_guide.md
+18-4
Original file line number
Diff line number
Diff line change
@@ -6,15 +6,29 @@ _Creating and deploying a new package version is easy!_
6
6
7
7
1. Ensure you're on the latest `master` branch
8
8
9
-
2. Ensure you have access to a PyPI account that is a maintainer of [scaleapi](https://pypi.org/project/scaleapi/) on PyPI
9
+
2. Ensure the master already has an incremented version
10
10
11
-
### Deployment Steps:
11
+
3.*(Required if you are manually publishing to PyPI)* Ensure you have access to a PyPI account that is a maintainer of [scaleapi](https://pypi.org/project/scaleapi/) on PyPI
12
12
13
-
**Step 0: Critical - Bump Project Version**
13
+
**How to Bump Project Version**
14
14
15
15
Ensure `_version.py` has an updated project version. If not, please increment the project version, commit and push the changes.
16
16
17
17
We use [semantic versioning](https://packaging.python.org/guides/distributing-packages-using-setuptools/#semantic-versioning-preferred). If you are adding a meaningful feature, bump the minor version. If you are fixing a bug, bump the incremental version.
18
+
### Deployment:
19
+
20
+
21
+
#### Automated Deployment and Publish with CircleCI:
22
+
23
+
Our repo already has a publish worklow built into the CircleCI. It's trigerred when there's a new release on GitHub, with a specific version tag.
24
+
25
+
In order to deploy and publish a new version:
26
+
- Create a new [Release](https://github.com/scaleapi/scaleapi-python-client/releases) on GitHub
27
+
- Create and assign a new tag in the release page with the following template: `vX.Y.Z` Please make sure `X.Y.Z` is matching the version in the `_version.py`.
28
+
-*i.e.* If the version in `_version.py` is **2.3.1** then the tag should be **v2.3.1**
29
+
- Provide release notes by following the [Release Notes Template](release_notes_template.md) and filling relevant sections to your changes.
30
+
#### *(Unpreferred)* Manual Deployment and Publish:
Create a [new release](https://github.com/scaleapi/scaleapi-python-client/releases/new) on GitHub with a matching version tag _(i.e. v2.0.1)_. Please provide a summary about new features and fixed bugs in the Release Notes.
53
+
Create a [new release](https://github.com/scaleapi/scaleapi-python-client/releases/new) on GitHub with a matching version tag _(i.e. v2.0.1)_. Provide release notes by following the [Release Notes Template](release_notes_template.md)and filling relevant sections to your changes.
0 commit comments