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
Leveraging GitHub Workflows, maintainers can release new versions of Birdy automatically:
71
+
72
+
* Ensure that the changelog and version on the main development branch have been updated to reflect the new version.
73
+
* Create a tag (`vX.Y.Z`) of the main development branch and push to the GitHub repository.
74
+
* This will trigger a workflow that will attempt to build Birdy and publish it to TestPyPI.
75
+
* When this actions succeeds, be sure to verify on TestPyPI that the package reflects changes.
76
+
* On GitHub, a maintainer can then publish a new version using the newly created tag.
77
+
* This will trigger a workflow that will attempt to build Birdy and publish it to PyPI.
78
+
* Be warned that once published to PyPI, a version number can never be overwritten! Bad versions may only be `yanked <https://pypi.org/help/#yanked>`_.
0 commit comments