[changelog] [Added] New changes field added to Bitbucket Forge PR update event

[nyxthedev]

GUID: CHANGE-3435
pubDate: Thu, 10 Sep 2026 22:54:26 GMT
Category: Added

What's changing

Bitbucket pull request update events delivered to Forge apps now include an additional changes field in the payload. The field is present when a PR is updated because a new commit was pushed to the source branch, letting apps distinguish code-level updates (new commits) from metadata updates (title/description changes). Backward-compatible: no existing fields removed or renamed. Apps validating payloads with a strict schema should allow the new changes property. Updated payload structures are in the Bitbucket pull request updated event reference documentation.

Impact on forge-sim parity

Simulator area: triggers / product events (event payload shapes fired via forge_fire_trigger and trigger handler simulation).

• If forge-sim ships or documents sample payloads for the Bitbucket PR updated event (avi:bitbucket:updated:pullrequest), those fixtures should gain the changes field for commit-push updates so apps tested locally see the same shape they'll see in production.
• Any payload validation or typing around Bitbucket PR events should permit changes.
• This modifies the documented payload of an existing event (conditional new field), so parity docs/spec rows covering that event payload need updating.

Link: https://developer.atlassian.com/platform/forge/changelog/#CHANGE-3435

• forge-spec: update affected requirement rows (behavior change)