Additional fields in Bitbucket Forge events
- Announced
- APIs
- forge-bitbucket, rest-bitbucket-cloud
- Severity
- notable, set by
reef/atlassian-rule-v1 - Source
- https://developer.atlassian.com/changelog/#CHANGE-3330
Additional fields available in Bitbucket Forge events. This change is backward-compatible; no existing fields are removed or renamed.
What’s changing:
Bitbucket Forge events now include additional fields in their payloads. This update allows Forge apps to access more comprehensive data directly from the event, reducing the need to make separate API calls back to Bitbucket to fetch missing details.
The following event types are updated with additional fields:
- Repository created events
- Repository push events
- Build status events
- Pull request events
What you need to do:
No action is required. If your app is already listening to these Bitbucket Forge events, the additional fields will automatically be available in the event payload. If you validate event payloads with a strict schema, ensure your validator allows additional properties.
You can review the updated payload structures in the Bitbucket events reference documentation.
The text above is Atlassian's. reef added the severity, the dates it could read from the text, and the endpoints and scopes named in code.