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

Open
#29 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
65/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
typescript
Domain
tooling

Research direction

Start with the forge-spec affected requirement rows and the manifest/modules handling for the Confluence macro module. Check how validation currently treats the categories property, then compare the needed category transition with the linked Forge changelog. Done means the manifest schema reflects the singular property and the transition behavior is documented or enforced as specified.

Written by the indexing model from the issue text.

Description

upstream-changelog

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)
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.