Files
Larsen Cundric 1186d4cc44 publish: gate publish_to_pypi behind release env
browser-use ships to PyPI via OIDC trusted-publishing today, but the
publish job had no environment gate — anyone with workflow-dispatch
access (or any token with workflow scope) could trigger a publish
single-handedly. Adds:

- environment: release on publish_to_pypi
  Reviewers configured separately on the env: gregpr07, MagMueller,
  sauravpanda. prevent_self_review:true so the dispatcher cannot
  self-approve.

- Fail-closed preflight that verifies the env still has required
  reviewers and prevent_self_review enabled before publishing.
  Same check the sdk pipeline uses. Guards against silent env
  config drift.

- actions: read permission on the publish job for the env check.

Does NOT change the trigger model (release:published + workflow_dispatch),
does NOT touch tag_pre_release, does NOT touch the trusted-publishing
publish command itself. Minimal change, single security win:
two-person rule on every PyPI release.

Refs ENG-4762.
2026-06-10 15:31:33 +02:00
..
2025-06-17 22:38:59 -07:00
2025-06-09 22:34:34 -07:00