feat: Add pypi actions

[fsbraun]

Description

Adds actions for pypi publication.

Related resources

• ...

• ...

Checklist

• [ ] I have opened this pull request against master
• [ ] I have added or modified the tests when changing logic
• [ ] I have followed the conventional commits guidelines to add meaningful information into the changelog
• [ ] I have read the contribution guidelines and I have joined #workgroup-pr-review on Slack to find a “pr review buddy” who is going to review my pull request.

[codecov[bot]]

Codecov Report

Merging #335 (19d40ff) into master (3df6225) will not change coverage. The diff coverage is 100.00%.

:exclamation: Current head 19d40ff differs from pull request most recent head 1b248a7. Consider uploading reports for the commit 1b248a7 to get more accurate results

@@           Coverage Diff           @@
##           master     #335   +/-   ##
=======================================
  Coverage   90.93%   90.93%           
=======================================
  Files          72       72           
  Lines        2536     2536           
  Branches      358      358           
=======================================
  Hits         2306     2306           
  Misses        170      170           
  Partials       60       60           

Impacted Files	Coverage Δ
djangocms_versioning/__init__.py	100.00% <100.00%> (ø)

[marksweb]

To fix the ruff error, the pyupgrade part of the config needs removing

[marksweb]

@fsbraun because this is going to be new to pypi, I'd need a generic token so this has got me thinking about this new trusted publishing method of deployment.

Looking at the action repo, it's actually a simpler workflow to work this way so I'd like to swap to this style.

https://github.com/pypa/gh-action-pypi-publish#trusted-publishing

It looks like the setup is this simple for live;

name: Publish Python 🐍 distributions 📦 to pypi

on:
  release:
    types:
      - published

jobs:
  build-n-publish:
    name: Build and publish Python 🐍 distributions 📦 to pypi
    runs-on: ubuntu-latest
    environment:
      name: pypi
      url: https://pypi.org/p/djangocms-versioning
    permissions:
      id-token: write
    steps:
    - uses: actions/checkout@v3
    - name: Set up Python 3.10
      uses: actions/setup-python@v4
      with:
        python-version: '3.10'

    - name: Install pypa/build
      run: >-
        python -m
        pip install
        build
        --user
    - name: Build a binary wheel and a source tarball
      run: >-
        python -m
        build
        --sdist
        --wheel
        --outdir dist/
        .

    - name: Publish distribution 📦 to PyPI
      if: startsWith(github.ref, 'refs/tags')
      uses: pypa/gh-action-pypi-publish@release/v1

And the test release...

name: Publish Python 🐍 distributions 📦 to TestPyPI

on:
  push:
    branches:
      - master

jobs:
  build-n-publish:
    name: Build and publish Python 🐍 distributions 📦 to TestPyPI
    runs-on: ubuntu-latest
    environment:
      name: pypi
      url: https://pypi.org/p/djangocms-versioning
    permissions:
      id-token: write
    steps:
    - uses: actions/checkout@v3
    - name: Set up Python 3.10
      uses: actions/setup-python@v4
      with:
        python-version: '3.10'

    - name: Install pypa/build
      run: >-
        python -m
        pip install
        build
        --user
    - name: Build a binary wheel and a source tarball
      run: >-
        python -m
        build
        --sdist
        --wheel
        --outdir dist/
        .

    - name: Publish distribution 📦 to Test PyPI
      uses: pypa/gh-action-pypi-publish@release/v1
      with:
        repository-url: https://test.pypi.org/legacy/
        skip_existing: true

[fsbraun]

@marksweb Done!

[fsbraun]

@marksweb Can you mark your comment as resolved so that I can merge it?