Skip to content

Use separate GitHub environment for deploy workflows #10871

@bluetech

Description

@bluetech

Reading this page https://docs.pypi.org/trusted-publishers/security-model/#considerations they mention:

Use a dedicated environment: GitHub Actions supports "environments," which can be used to isolate secrets to specific workflows. OIDC publishing doesn't use any pre-configured secrets, but a dedicated publish or deploy environment is a general best practice.

Dedicated environments allow for additional protections like required reviewers, which can be used to require manual approval for a workflow using the environment.

Seems like a good idea to segregate the deployment secrets to their own environment and add required reviewers (probably pytest core?) to better protect our releases.

I can try to set it up before the next release (#10869) if we agree.

Metadata

Metadata

Assignees

Labels

type: infrastructureimprovement to development/releases/CI structure

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions