Publishing
==========

Every pushed commit installs the package, compiles the Python sources, runs the
module tests, builds the distribution, and validates it with ``twine check``.
Only branches named with the Tryton series, such as ``8.0``, continue to the
publishing step after those checks pass.

The publishing workflow creates a CI-only package version by reading the
published versions in Gitea's PyPI-compatible package registry and assigning the
next patch version for the branch series. For example, branch ``8.0`` publishes
``8.0.0`` when no package exists yet, then ``8.0.1``, ``8.0.2``, and so on.

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:

* ``REGISTRY_USER``
* ``REGISTRY_PASSWORD``

Publish a release branch:

.. code-block:: console

   git switch 8.0
   git push origin 8.0

Install from Gitea:

.. code-block:: console

   pip install \
     --index-url https://gitea.joseagrc.com/api/packages/tryton-do/pypi/simple \
     trytond_account_do