Skip to content

chore: migrate PyPI publishing workflow to OSS Exit Gate - #712

Open
zarturod wants to merge 1 commit into
google:masterfrom
zarturod:chore/oss-exit-gate-migration
Open

zarturod wants to merge 1 commit into
google:masterfrom
zarturod:chore/oss-exit-gate-migration

Conversation

@zarturod

@zarturod zarturod commented Nov 5, 2026

Copy link
Copy Markdown

Summary

Migrates the PyPI publishing job in .github/workflows/build.yml for s2geometry to publish through Google's OSS Exit Gate (s2geometry/pypi).

Changes

  • Adds contents: read alongside id-token: write and attestations: write on the PyPI publish job (keeping build provenance attestation intact).
  • Replaces pypa/gh-action-pypi-publish with SHA-pinned Google Cloud Workload Identity Federation (google-github-actions/auth@7c6bc770dae815cd3e89ee6cdf493a5fab2cc093 # v3.0.0, provider projects/305452601764/locations/global/workloadIdentityPools/builders/providers/github).
  • Stages wheel and sdist artifacts (dist/*) in an isolated .exit-gate-venv virtualenv to https://us-python.pkg.dev/oss-exit-gate-prod/s2geometry--pypi using twine and keyrings.google-artifactregistry-auth.
  • Uploads the release manifest to gs://oss-exit-gate-prod-projects-bucket/s2geometry/pypi/manifests/manifest-${{ github.run_id }}-${{ github.run_attempt }}.json to trigger the OSS Exit Gate release pipeline.

Verification (Step 8 Production Smoke Test)

  • Production onboarding config (s2geometry/pypi, http://cl/1013237205) and Terraform provisioning (http://cl/1013331879) are live.
  • End-to-end Artifact Registry staging (s2geometry==0.14.0, HTTP 200) and GCS manifest upload (HTTP 200) verified.

Refs: b/579643398, b/576680589

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant