Skip to content

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

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

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

Conversation

@zarturod

@zarturod zarturod commented Nov 4, 2026

Copy link
Copy Markdown

Summary

Migrates the existing .github/workflows/publish.yml PyPI release workflow for xee to publish through Google's OSS Exit Gate (xee/pypi).

Changes

  • Replaces direct pypa/gh-action-pypi-publish upload with Google Cloud Workload Identity Federation (google-github-actions/auth@7c6bc770dae815cd3e89ee6cdf493a5fab2cc093 # v3.0.0, provider projects/305452601764/locations/global/workloadIdentityPools/builders/providers/github).
  • Stages built wheels and sdist (dist/*) to the OSS Exit Gate Artifact Registry (https://us-python.pkg.dev/oss-exit-gate-prod/xee--pypi) using twine and keyrings.google-artifactregistry-auth.
  • Uploads publish_all.json to gs://oss-exit-gate-prod-projects-bucket/xee/pypi/manifests/manifest-${{ github.run_id }}-${{ github.run_attempt }}.json to trigger the OSS Exit Gate release pipeline (preserving the existing if: github.event_name == 'release' || !inputs.dry_run guard).

Verification & Internal CLs

  • Production onboarding config (//depot/google3/configs/security/opensource/exit_gate/prod/projects/xee/pypi/project.txtpb, http://cl/1013200563) is live.
  • Step 8 production smoke test (xee==0.1.2 Artifact Registry staging + GCS manifest upload) passed (HTTP 200).
  • Step 10 Handoff CL: http://cl/1014014567

Refs: b/579426084, b/576680589

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