Skip to content

Commit 60e1ba5

Browse files
committed
Build with "build" like Github does
This allow to have the same build which result in bit-for-bit identical artifact between Github and local build.
1 parent 29c97e4 commit 60e1ba5

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

CONTRIBUTING.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -97,13 +97,13 @@ The process to make a release is the following:
9797
* Check that documentation build (`cd docs; make clean html`)
9898
* Bump the version number in ``paho/mqtt/__init__.py``, commit the change.
9999
* Make a dry-run of build:
100-
* Build using hatch: ``python -m hatch build``
100+
* Build release: ``python -m build .``
101101
* Check with twine for common errors: ``python -m twine check dist/*``
102102
* Try uploading it to testpypi: ``python3 -m twine upload --repository testpypi dist/*``
103103
* Do a GPG signed tag (assuming your GPG is correctly configured, it's ``git tag -s -m "Version 1.2.3" v1.2.3``)
104104
* Push the commit and it's tag to Github
105105
* Make sure your git is clean, especially the ``dist/`` folder.
106-
* Build a release: ``python -m hatch build``
106+
* Build a release: ``python -m build .``
107107
* You can also get the latest build from Github action. It should be identical to your local build:
108108
https://github.com/eclipse/paho.mqtt.python/actions/workflows/build.yml?query=branch%3Amaster
109109
* Then upload the dist file, you can follow instruction on https://packaging.python.org/en/latest/tutorials/packaging-projects/#uploading-the-distribution-archives

0 commit comments

Comments
 (0)