v1.2.13 #41

	# This workflow will upload a Python Package using Twine when a release is created
	# For more information see: https://docs.github.com/en/actions/automating-builds-and-tests/building-and-testing-python#publishing-to-package-registries

	# This workflow uses actions that are not certified by GitHub.
	# They are provided by a third-party and are governed by
	# separate terms of service, privacy policy, and support
	# documentation.

	name: Upload Python Package

	on:
	release:
	types: [published]

	permissions:
	contents: read

	jobs:
	deploy:
	runs-on: ubuntu-latest

	steps:
	- uses: actions/checkout@v3
	- name: Install Python
	uses: actions/setup-python@v4
	- name: Install poetry
	uses: abatilo/actions-poetry@v2
	- name: Setup a local virtual environment (if no poetry.toml file)
	run: \|
	poetry config virtualenvs.create true --local
	poetry config virtualenvs.in-project true --local
	- uses: actions/cache@v3
	name: Define a cache for the virtual environment based on the dependencies lock file
	with:
	path: ./.venv
	key: venv-${{ hashFiles('poetry.lock') }}
	- name: Install the project dependencies
	run: poetry install
	- name: stamp version
	run: poetry version ${{ github.ref_name }}
	- name: Build package
	run: poetry build
	- name: set secret
	run: poetry config pypi-token.pypi ${{ secrets.PYPI_API_TOKEN }}
	- name: Publish package
	run: poetry publish

Provide feedback