8000 ci(release): migrate google-vizier-dev PyPI publishing to OSS Exit Gate by alonsopf89 · Pull Request #1339 · google/vizier · GitHub
[go: up one dir, main page]

Skip to content

ci(release): migrate google-vizier-dev PyPI publishing to OSS Exit Gate - #1339

Open
alonsopf89 wants to merge 1 commit into
google:mainfrom
alonsopf89:oss-exit-gate-pypi-migration
Open

alonsopf89 wants to merge 1 commit into
google:mainfrom
alonsopf89:oss-exit-gate-pypi-migration

Conversation

@alonsopf89
Copy link
Copy Markdown

Summary

Migrates .github/workflows/pypi-publish-dev.yml PyPI publishing (google-vizier-dev) to Google OSS Exit Gate (vizier/pypi) via keyless Workload Identity Federation (OIDC):

  • Authenticates via SHA-pinned google-github-actions/auth and google-github-actions/setup-gcloud (no static PyPI secrets).
  • Performs safe, version-scoped cleanup of any failed staging attempt for the exact version being built (gcloud artifacts versions delete).
  • Stages built distributions to https://us-python.pkg.dev/oss-exit-gate-prod/vizier--pypi/ via twine and uploads the release manifest to gs://oss-exit-gate-prod-projects-bucket/vizier/pypi/manifests/.
  • (Note: pypi-publish.yml for stable google-vizier releases is intentionally untouched in this PR; we can authorize pypi-publish.yml in the Step 10 ownership handoff CL and migrate it in a follow-up PR once confirmed.)

One-time PyPI Trusted Publisher setup (before next release)

Add vizier-py@oss-exit-gate-prod.iam.gserviceaccount.com as a Google Cloud Trusted Publisher on PyPI (https://pypi.org/manage/project/google-vizier-dev/settings/publishing/).

Verification

  • Internal Exit Gate onboarding config (http://cl/1024944855) is submitted in #head and staging resources are provisioned.
  • End-to-end Step 8 smoke test (publish_all: false) passed against vizier--pypi and staged test artifacts were cleaned up.

Internal Reference (for Google maintainers):

  • Documentation & Migration Guide: http://go/oss-exit-gate (internal to google3; there is no public repo under github.com/google)
  • Buganizer Tracking Issue: http://b/576673325 (Parent Epic: http://b/576673325)
  • Internal Onboarding CL: http://cl/1024944855

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

0