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
+22-5Lines changed: 22 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -51,13 +51,30 @@ Ready to contribute? Here's how to set up `aicsshparam` for local development.
51
51
## Deploying
52
52
53
53
A reminder for the maintainers on how to deploy.
54
-
Make sure all your changes are committed.
55
-
Then run:
56
54
55
+
1. **Ensure all changes are committed.**
56
+
Refer to [bump2version on PyPI](https://pypi.org/project/bump2version/) for more details on versioning.
57
+
58
+
2. **Bump the version number.**
59
+
Run one of the following commands depending on the type of version update:
60
+
```bash
61
+
bump2version major # for major releases with breaking changes
62
+
bump2version minor # for minor releases with new features
63
+
bump2version patch # for patch releases with bug fixes
64
+
```
65
+
66
+
3. **Push the changes and tags to the repository.**
67
+
```bash
68
+
git push
69
+
git push --tags
70
+
```
71
+
72
+
---
73
+
74
+
**Note:**
75
+
Sometimes, you might encounter situations where there are uncommitted changes or modifications in your working directory that you intend to include in the release. In such cases, you can use the `--allow-dirty` flag with `bump2version` to permit version bumping even when the working directory isn't clean:
57
76
```bash
58
-
bump2version patch # possible: major / minor / patch
59
-
git push
60
-
git push --tags
77
+
bump2version patch --allow-dirty
61
78
```
62
79
63
80
This will release a new package version on Git + GitHub and publish to PyPI.
0 commit comments