You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Migrates .github/workflows/wheels.yml PyPI publishing (google-benchmark) to Google OSS Exit Gate (benchmark/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/benchmark--pypi/ via twine and uploads the release manifest to gs://oss-exit-gate-prod-projects-bucket/benchmark/pypi/manifests/.
One-time PyPI Trusted Publisher setup (before next release)
Add benchmark-py@oss-exit-gate-prod.iam.gserviceaccount.com as a Google Cloud Trusted Publisher on PyPI (https://pypi.org/manage/project/google-benchmark/settings/publishing/).
Verification
Internal Exit Gate onboarding config (http://cl/1024943651) is submitted in #head and staging resources are provisioned.
End-to-end Step 8 smoke test (publish_all: false) passed against benchmark--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)
I would expect such a change to be coming from someone whose github account is clearly associated
with either python or google org. How do we know this isn't a phishing change?
Hi @LebedevRI — completely fair question, thanks for being cautious!
I'm working with Google's Open Source Security / OSS Exit Gate team (fernandoalonso@google.com, verified by cla/google: SUCCESS on this PR) and coordinated internally with @dmah42 before opening this PR.
Any Google maintainer on google/benchmark can verify the onboarding internally via:
Also note that us-python.pkg.dev/oss-exit-gate-prod/benchmark--pypi/ is Google-owned Artifact Registry staging infrastructure, and PyPI will not accept releases from Exit Gate unless the google-benchmark PyPI maintainers explicitly authorize benchmark-py@oss-exit-gate-prod.iam.gserviceaccount.com as a Trusted Publisher.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Migrates
.github/workflows/wheels.ymlPyPI publishing (google-benchmark) to Google OSS Exit Gate (benchmark/pypi) via keyless Workload Identity Federation (OIDC):google-github-actions/authandgoogle-github-actions/setup-gcloud(no static PyPI secrets).gcloud artifacts versions delete).https://us-python.pkg.dev/oss-exit-gate-prod/benchmark--pypi/viatwineand uploads the release manifest togs://oss-exit-gate-prod-projects-bucket/benchmark/pypi/manifests/.One-time PyPI Trusted Publisher setup (before next release)
Add
benchmark-py@oss-exit-gate-prod.iam.gserviceaccount.comas a Google Cloud Trusted Publisher on PyPI (https://pypi.org/manage/project/google-benchmark/settings/publishing/).Verification
http://cl/1024943651) is submitted in#headand staging resources are provisioned.publish_all: false) passed againstbenchmark--pypiand staged test artifacts were cleaned up.Internal Reference (for Google maintainers):
http://go/oss-exit-gate(internal togoogle3; there is no public repo undergithub.com/google)http://b/576673325(Parent Epic:http://b/576673325)http://cl/1024943651