Releases are currently built and uploaded by hand with twine from a maintainer's workstation, which makes the process depend on one person's environment and on a long-lived PyPI token.
A tag-triggered GitHub Actions workflow using PyPI Trusted Publishing would remove the stored credential and make releases reproducible.
Worth including in the same workflow: updating the Spack recipe in ebrains-spack-builds.
Releases are currently built and uploaded by hand with twine from a maintainer's workstation, which makes the process depend on one person's environment and on a long-lived PyPI token.
A tag-triggered GitHub Actions workflow using PyPI Trusted Publishing would remove the stored credential and make releases reproducible.
Worth including in the same workflow: updating the Spack recipe in ebrains-spack-builds.