- Notifications
You must be signed in to change notification settings - Fork27
Commitaad344b
committed
add workflow to publish to PyPI
This workflow is triggered when publishing a new releaseusing the GitHub Releases functionality. It can also betriggered manually for testing.The workflow will always publish to Test PyPI, but willonly publish to the real PyPI, when releasing a newversion using the GitHub Releases functionality.The version for the package is generated by setuptools_scm,based on the git tags/commits. For all non-tagged commits,a "dev version" is generated with the format "0.1.2-dev3",where 0.1.2 is the latest tag plus one more in the last partof the version number (i.e. given the last tag was 0.1.1,0.1.2 will be used for the dev version) and the 3 in "-dev3"comes from the number of commits since the last tag.(This all is standard setuptools_scm behaviour.)1 parent6625e55 commitaad344b
1 file changed
+42
-0
lines changed| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
| 1 | + | |
| 2 | + | |
| 3 | + | |
| 4 | + | |
| 5 | + | |
| 6 | + | |
| 7 | + | |
| 8 | + | |
| 9 | + | |
| 10 | + | |
| 11 | + | |
| 12 | + | |
| 13 | + | |
| 14 | + | |
| 15 | + | |
| 16 | + | |
| 17 | + | |
| 18 | + | |
| 19 | + | |
| 20 | + | |
| 21 | + | |
| 22 | + | |
| 23 | + | |
| 24 | + | |
| 25 | + | |
| 26 | + | |
| 27 | + | |
| 28 | + | |
| 29 | + | |
| 30 | + | |
| 31 | + | |
| 32 | + | |
| 33 | + | |
| 34 | + | |
| 35 | + | |
| 36 | + | |
| 37 | + | |
| 38 | + | |
| 39 | + | |
| 40 | + | |
| 41 | + | |
| 42 | + | |
0 commit comments
Comments
(0)