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: README.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -66,7 +66,7 @@ Integration and unit tests are provided.
66
66
- Ensure that doc strings are updated in the code itself to work with Sphinx and are correctly formatted.
67
67
- Examples are always good especially if this a new feature or method.
68
68
- Think about a new user to the API trying to figure out how to use the features you're documenting.
69
-
3) Update the version value in `shotgun_api3/setup.py` to match the version you are packaging. This controls what version users will get when installing via pip.
69
+
3) Update the version value in `python-api/setup.py` to match the version you are packaging. This controls what version users will get when installing via pip.
70
70
4) Update the `__version__` value in `shotgun_api3/shotgun.py` to the version you're releasing. This identified the current version within the API itself.
71
71
5) Commit these changes in master with a commit message like `packaging for the vx.x.x release`.
72
72
6) Create a tag based off of the master branch called `vx.x.x` to match the version number you're releasing.
0 commit comments