We’re implementing an auth layer for our Forge Remote integration and we got caught out today by an unexpected change in the shape of license information on Forge Invocation Tokens. Previously we were adhering to the shape of the license listed on the FIT section here: Forge Remote essent…

Hi @GeorgeScott - thanks for bringing this to the community’s attention. I am chasing down more details to see if I can share what has happened here and how we can improve going forward.

This change was unintentionally missed from our changelog. A retroactive announcement will be added today. Because this change was additive, it did not get flagged as requiring a deprecation period. I’m sorry for the pain this caused you! We’ll strive to do better.

I have tried to get clarity on that contract before as well, but we unfortunately never received a response. I mentioned a couple of times that reading and parsing the context in a Forge or Forge Remote invocation is one of the most fragile parts of Forge apps, because SDK types are very generic an…

Sorry about this @tbinna - let me follow up on this, too.

active - Atlassian developer changelog The license objects in app context and FIT have a new .css-9z42f9{font-size:0.875em;font-family:'SFMono-Medium','SF Mono','Segoe UI Mono','Roboto Mono','Ubuntu… | This page contains announcements and updates for developers from various products,... …

Just for clarity, does this change also apply to the context.license object available in resolver functions? import { makeResolver } from "@forge/resolver"; interface ExampleRequest { payload: ExamplePayload; context: Context } interface ResolverDefinitions { example: (args: ExamplePayload)…

Just for clarity, does this change also apply to the context.license object available in resolver functions? We’ve updated the documentation to fix the missing reference to the LicenseDetails type in the resolver function signature: https://developer.atlassian.com/platform/forge/runtime-referenc…

Hi @HeyJoe , Could you clarify what happens to old versions of Forge apps? Does it only apply to latest version or are you supposed to go back and backport this to each and every major release that was done in the past?

The Atlassian Developer Community

Clarity on Forge License shape in APIs

Forge

HeyJoe May 12, 2026, 5:06am 21

Good catch. This is being fixed now.