@@ -26,27 +26,12 @@ new version number.
2626
27273 . Add release notes to ` bindings/python/CHANGELOG.md ` . Generally just
2828 summarize/clarify the git log, but you might add some more long form
29- notes for big changes.
29+ notes for big changes. Replace the ` devN ` version number w/ the new version
30+ number (see note above in [ Versioning] ( #versioning ) ). Make sure version number
31+ is updated in ` pymongoarrow/version.py ` . Create a PR with the changelog and version
32+ update.
3033
31- 4 . Replace the ` devN ` version number w/ the new version number (see
32- note above in [ Versioning] ( #versioning ) ). Make sure version number
33- is updated in ` pymongoarrow/version.py ` . Commit the change and tag
34- the release. Immediately bump the version number to ` dev0 ` in a new
35- commit:
36-
37- $ # Bump to release version number
38- $ git commit -a -m "BUMP <release version number>"
39- $ git tag -a "<release version number>" -m "BUMP <release version number>"
40- $ # Bump to dev version number
41- $ git commit -a -m "BUMP <dev version number>"
42- $ git push
43- $ git push --tags
44-
45- 5 . Pushing a tag will trigger the release process on GitHub Actions
46- that will require a member of the team to authorize the deployment.
47- Navigate to
48- < https://github.com/mongodb-labs/mongo-arrow/actions/workflows/release-python.yml >
49- and wait for the publish to complete.
34+ 5 . Run the release workflow: https://github.com/mongodb-labs/mongo-arrow/actions/workflows/release-python.yml .
5035
51366 . Make sure the new version appears on
5237 < https://mongo-arrow.readthedocs.io/en/stable/ > . If the new version
@@ -58,8 +43,7 @@ new version number.
58438 . Announce the release on:
5944 < https://www.mongodb.com/community/forums/c/announcements/driver-releases >
6045
61- 9 . Create a GitHub Release for the tag using
62- < https://github.com/mongodb/mongo-arrow/releases/new > . The title
46+ 9 . Publish the draft GitHub Release for the tag. The title
6347 should be "PyMongoArrow X.Y.Z", and the description should contain a
6448 link to the release notes on the the community forum, e.g. "Release
6549 notes:
0 commit comments