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
{{ message }}
This repository was archived by the owner on May 27, 2024. It is now read-only.
@@ -83,55 +92,8 @@ Before making a release, you need to update the version number in the `pyproject
83
92
>
84
93
> Additional labels for pre-release and build metadata are available as extensions to the MAJOR.MINOR.PATCH format.
85
94
86
-
Once you are done, run
87
-
88
-
```
89
-
git push --tags
90
-
```
91
-
92
-
to publish the created tag on GitHub. Alternatively, it is possible to create a tag through the Github web interface. For more information, see [managing Github releases][]. This will automatically trigger a Github workflow that creates a release on PyPI.
93
-
94
-
### The release Github workflow
95
-
96
-
#### Behind the scenes
97
-
98
-
This section explains how releases can be created manually purely for educational purposes. Experienced developers may skip this section.
99
-
Python packages are not distributed as source code, but as _distributions_. The most common distribution format is the so-called _wheel_. To build a _wheel_, run
100
-
101
-
```bash
102
-
python -m build
103
-
```
104
-
105
-
This command creates a _source archive_ and a _wheel_, which are required for publishing your package to [PyPI][]. These files are created directly in the root of the repository.
106
-
107
-
Before uploading them to [PyPI][] you can check that your _distribution_ is valid by running:
108
-
109
-
```bash
110
-
twine check dist/*
111
-
```
112
-
113
-
and finally publishing it with:
114
-
115
-
```bash
116
-
twine upload dist/*
117
-
```
118
-
119
-
Provide your username and password when requested and then go check out your package on [PyPI][]!
120
-
121
-
For more information, follow the [Python packaging tutorial][].
122
-
123
-
#### Configuring the Github workflow
124
-
125
-
Tags adhering to `"*.*.*"` that are pushed to the `main` branch will trigger the release Github workflow that automatically builds and uploads the Python package to [PyPI][].
126
-
For this to work, the `PYPI_API_TOKEN` Github secret needs to be set to the value of the [PyPI][] token.
127
-
See [Creating PyPI tokens][] for instructions on how to create a [PyPI][] token.
128
-
Finally, set your `PYPI_API_TOKEN` Github secret equal to the value of the just created [PyPI][] token by following [creating Github secrets][].
Once you are done, commit and push your changes and navigate to the "Releases" page of this project on GitHub.
96
+
Specify `vX.X.X` as a tag name and create a release. For more information, see [managing GitHub releases][]. This will automatically create a git tag and trigger a Github workflow that creates a release on PyPI.
0 commit comments