[changelog] [Deprecation Notice] App macros will move to a single category as element browser categories are modernized #29

GUID: CHANGE-3409
Published: Tue, 25 Aug 2026 23:25:20 GMT
Category: Deprecation Notice

What's changing

In 6 months (25 Feb 2027), Forge app macros will only appear in one category in the modal element browser, and the categories ([string]) manifest property will be fully replaced by a new category (string) property for Forge app macros. Atlassian is also updating the slash menu and modal element browsers (rollout begins 06 Oct 2026). This impacts all apps using macros and requires action from app developers.

Impact on forge-sim parity

Simulator area: manifest / modules (Confluence macro module).

• If forge-sim's manifest parsing/validation for the macro module knows about categories ([string]), it needs to accept the new singular category (string) property.
• During the transition window both properties may appear in real-world manifests; after 25 Feb 2027 categories is deprecated/replaced. forge-sim should mirror whatever validation Forge's linter applies (accept category, eventually warn/reject categories in line with upstream behavior).
• Element browser presentation itself is a Confluence editor UI concern with no runtime surface to simulate, so the parity work is limited to manifest schema handling.

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

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