chore(ci): use poetry instead of pipenv #2

	name: Deploy documentation

	on:
	push:
	branches:
	- main
	- fix-python-build

	workflow_dispatch:

	permissions:
	contents: read
	pages: write
	id-token: write

	# Allow only one concurrent deployment, skipping runs queued between the run in-progress and latest queued.
	# However, do NOT cancel in-progress runs as we want to allow these production deployments to complete.
	concurrency:
	group: "pages"
	cancel-in-progress: false

	jobs:
	build:
	name: Build documentation website with MkDocs
	runs-on: ubuntu-latest
	steps:
	- name: Setup Python
	uses: actions/setup-python@v4
	with:
	python-version: "3.11"

	- name: Install poetry
	run: pip install -U poetry

	- name: Checkout
	uses: actions/checkout@v4
	with:
	submodules: recursive
	fetch-depth: 0

	- name: Install dependencies
	run: poetry install --no-root

	- name: Setup Pages
	id: pages
	uses: actions/configure-pages@v4

	- name: Build with mkdocs
	run: poetry run mkdocs build

	- name: Upload artifact
	uses: actions/upload-pages-artifact@v3
	with:
	path: ./site

	deploy:
	name: Deploy to GitHub Pages
	environment:
	name: github-pages
	url: ${{ steps.deployment.outputs.page_url }}
	runs-on: ubuntu-latest
	needs: build
	steps:
	- name: Deploy to GitHub Pages
	id: deployment
	uses: actions/deploy-pages@v4

Provide feedback