Publish package on every branch push

This commit is contained in:
José Arturo García
2026-07-22 19:22:43 -04:00
parent cf075aa4d9
commit ac4f674710
2 changed files with 7 additions and 5 deletions
+1 -1
View File
@@ -41,7 +41,6 @@ jobs:
publish: publish:
runs-on: ubuntu-latest runs-on: ubuntu-latest
needs: build needs: build
if: ${{ startsWith(github.ref, 'refs/heads/8.0.') }}
steps: steps:
- name: Checkout - name: Checkout
@@ -71,5 +70,6 @@ jobs:
TWINE_PASSWORD: ${{ secrets.GITEA_PACKAGE_TOKEN }} TWINE_PASSWORD: ${{ secrets.GITEA_PACKAGE_TOKEN }}
run: | run: |
python -m twine upload \ python -m twine upload \
--skip-existing \
--repository-url https://gitea.joseagrc.com/api/packages/tryton-do/pypi \ --repository-url https://gitea.joseagrc.com/api/packages/tryton-do/pypi \
dist/* dist/*
+6 -4
View File
@@ -1,17 +1,19 @@
Publishing Publishing
========== ==========
Every pushed commit builds and validates the package. Every pushed commit builds, validates, and publishes the package to the Gitea
PyPI-compatible package registry.
Packages are published to the Gitea PyPI-compatible package registry when the The publishing workflow uses ``twine upload --skip-existing`` so repeated
push is made to a version branch named like ``8.0.0``, ``8.0.1``, etc. commits with the same package version do not fail. To publish a new package
artifact, update the module version in ``tryton.cfg`` before pushing.
Required repository secrets: Required repository secrets:
* ``GITEA_PACKAGE_USER`` * ``GITEA_PACKAGE_USER``
* ``GITEA_PACKAGE_TOKEN`` * ``GITEA_PACKAGE_TOKEN``
Publish a release: Publish a release branch:
.. code-block:: console .. code-block:: console