Constrain dependencies in installer's base env more strictly (#187) #361

	name: deploy

	on:
	push:
	branches:
	- main
	tags:
	- "v" # Push events to matching v, i.e. v1.0, v20.15.10
	pull_request:
	branches:
	- main
	workflow_dispatch:

	jobs:

	deploy:
	# this will run when you have tagged a commit, starting with "v*"
	# and requires that you have put your twine API key in your
	# github secrets (see readme for details)
	if: ${{ github.repository == 'napari/packaging' && contains(github.ref, 'tags') }}
	runs-on: ubuntu-latest
	steps:
	- uses: actions/checkout@v4
	- name: Set up Python
	uses: actions/setup-python@v5
	with:
	python-version: "3.x"
	- name: Install dependencies
	run: \|
	python -m pip install --upgrade pip
	pip install build twine
	- name: Build and publish
	env:
	TWINE_USERNAME: __token__
	TWINE_PASSWORD: ${{ secrets.TWINE_API_KEY }}
	run: \|
	git tag
	cd constructor-manager
	python -m build
	twine check dist/*
	twine upload dist/*
	cd ..
	cd constructor-manager-cli
	python -m build
	twine check dist/*
	twine upload dist/*
	cd ..
	cd constructor-manager-ui
	python -m build
	twine check dist/*
	twine upload dist/*

Provide feedback