Deployment source enum: 'api' removed, replaced with 'rest-api', 'deploy-hook', 'integration'
BreakingBreaking change
This is a breaking change — integrations that rely on the affected behaviour will need updates before the change rolls out.
What changed
The "api" enum value in the sources field (used to filter/identify deployment trigger mechanisms) has been removed and replaced with three more specific values: "rest-api", "deploy-hook", and "integration". Any client that sends or checks for "api" as a deployment source — e.g. in deployment protection policies or filtering — will break, since "api" is no longer a valid enum member. The new values allow finer-grained control: "rest-api" covers direct REST API uploads, "deploy-hook" covers deploy-hook URL triggers, and "integration" covers OAuth2/integration-actor deployments.