Closed rajadain closed 5 months ago
The python-omgeo
Python packages is published via the Azavea PyPI account, however recent builds of these projects are failing because PyPI has changed from username/password authentication to token based and trusted-publisher based authentication. This workplan is to document updating this integration.
TestPyPi Python Package Index
credentials within 1Passwordazavea
user in the top-right hand corner, then select Your Projects
from the dropdown menuPublishing
, then scroll down to Add a new publisherNext
[!Note] Only use the actual repository name, not full GitHub URL nor the
azavea/
prefix.
Python Package Index (PyPi)
credentials within 1Passwordrelease.yml
GitHub Workflow to upload the release to TestPyPI
[!Tip] Review PR #72 to see what changes in the file were made/needed.
CHANGES.txt
file to document the updaterelease.yml
file to instead upload the release to PyPILow Risk
With recent changes to PyPI trusted publishers, we need to update the CI to use that instead of the old non-functional username / password setup.
Update the integration so that releases may publish to PyPI again.