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: developer/release.rst
+2-2
Original file line number
Diff line number
Diff line change
@@ -5,7 +5,7 @@ If you are developing a Python package containing colcon extensions you might wa
5
5
Commonly that involves bumping the version number and tagging the commit with that version.
6
6
7
7
Commonly Python packages are released to PyPI following the `packaging instructions for Python projects <https://packaging.python.org/tutorials/packaging-projects/>`_.
8
-
For colcon packages the recommendation is to use `publish-python <https://github.com/dirk-thomas/publish-python>`_ which not only uploads a wheel to PyPI but also creates and uploads Debian packages.
8
+
For colcon packages the recommendation is to use `publish-python <https://github.com/colcon/publish-python>`_ which not only uploads a wheel to PyPI but also creates and uploads Debian packages.
9
9
10
10
First-time setup
11
11
----------------
@@ -17,7 +17,7 @@ Before using ``publish-python`` you need to do the following:
17
17
* Configure credentials for packagecloud.io and request to be added as a contributor to the `colcon repository <https://packagecloud.io/dirk-thomas/colcon>`_
18
18
* Create a configuration file for your package
19
19
20
-
For details please see the `publish-python documentation <https://github.com/dirk-thomas/publish-python/blob/main/README.rst>`_.
20
+
For details please see the `publish-python documentation <https://github.com/colcon/publish-python/blob/main/README.rst>`_.
21
21
22
22
Example configuration file ``publish-python.yaml``:
0 commit comments