Use CI post version for Gitea package uploads
This commit is contained in:
+6
-3
@@ -6,9 +6,12 @@ PyPI-compatible package registry. The workflow intentionally does not use
|
||||
``actions/upload-artifact`` because current Gitea Actions runners do not support
|
||||
the GitHub artifact API required by ``upload-artifact@v4``.
|
||||
|
||||
The publishing workflow uses ``twine upload --skip-existing`` so repeated
|
||||
commits with the same package version do not fail. To publish a new package
|
||||
artifact, update the module version in ``tryton.cfg`` before pushing.
|
||||
The publishing workflow creates a CI-only package version by appending the run
|
||||
number to the module version from ``tryton.cfg``. For example, a module version
|
||||
of ``8.0.0`` is published as ``8.0.0.post123`` on run number ``123``.
|
||||
|
||||
This is necessary because Gitea's PyPI-compatible registry is a custom package
|
||||
repository for Twine and does not support ``twine upload --skip-existing``.
|
||||
|
||||
Required repository secrets:
|
||||
|
||||
|
||||
Reference in New Issue
Block a user