@forge/api @forge/bridge @forge/kvs major versions without changelog

Hi,

I’m in the process of updating my app dependencies. I noticed 3 major releases:

@forge/api: 5.2.0 => 6.0.0
@forge/bridge: 4.5.2 => 5.1.0
@forge/kvs: 0.1.2 => 1.0.0

Is there any documentation around what breaking changes were released?

I found this information for @forge/events 1.x => 2.x here https://developer.atlassian.com/platform/forge/runtime-reference/async-events-api-version-2-upgrade/

Thanks!

2 Likes

I’ve noticed references for these get sprinkled in as part of the https://developer.atlassian.com/changelog/# . Sometimes mentioning the package name explicitly, other times implied. Typically if there is a doc for navigating sweeping breaking changes, they reference it here. You can also find a change file inside the package that can include hints to the changes to check the respective specification doc.

@DavidPezet1 I can see the CHANGELOG.md inside two packages. Thanks for the hint :folded_hands:

@forge/api: 5.2.0 => 6.0.0 Major changes:

  • Update the package to build on Node 20

@forge/bridge: 4.5.2 => 5.1.0 Major changes:

  • Add emitReadyEvent to signal macro readiness

@forge/kvs: No CHANGELOG.md file

2 Likes