Skip to content

Release_Mangement

Jump to bottom
Andreas Dvorak edited this page Oct 8, 2026 · 3 revisions

Release Management process

Create a release

For the release number is used the semantic versioning: MAJOR.MINOR.PATCH

The GitHub action python-publish creates the package and does the upload to PyPi

These files are created

  • playbook_scheduler-1.0.0.tar.gz
  • playbook_scheduler-1.0.0-py3-none-any.whl

To install the pip

pip install playbook-scheduler

or to update

pip install --upgrade playbook-scheduler

toml version

In the file pyproject.toml the version for the release needs to be set.

version = "0.3.1"

Test PyPI

To test the installation from test.pypi.org you need to do two installation because not all dependencies are available in test.pypi.org

python -m pip install --index-url https://pypi.org/simple/ \
  "APScheduler>=3.10,<4" "Jinja2>=3.1" "PyYAML>=6.0"

python -m pip install --index-url https://test.pypi.org/simple/ \
  --no-deps playbook-scheduler

Clone this wiki locally