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

Open
#35 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
68/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
typescript
Domain
devtools, testing

Research direction

Start at the forge_fire_trigger handling and simulator fixtures for avi:bitbucket:updated:pullrequest, then inspect any payload validation or typing and forge-spec requirement rows for that event. Add the conditional changes field for commit-push updates and update the related parity documentation; done means local simulated payloads and validation accept the production shape.

Written by the indexing model from the issue text.

Description

upstream-changelog

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)
Dominant language
TypeScript
Stars
5
Forks
2
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from ryanackley/forge-sim

All issues in ryanackley/forge-sim

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.