GUID: CHANGE-3422
Published: Wed, 16 Sep 2026 01:16:18 GMT
Category: Announcement
What's changing
Atlassian has removed support for the bare forge webtrigger root command for creating web trigger URLs; the deprecation window has passed. The command now requires an explicit sub-command. To create a web trigger URL via the CLI you must use:
forge webtrigger create
# or
forge webtrigger create --functionKey <your-function-key>
Running the root command to generate a URL no longer works.
Parity impact for forge-sim
Simulator area: web triggers / CLI local-dev semantics.
- forge-sim's web trigger surface (
forge_fire_web_trigger, the dev server /__trigger/<key> endpoint) doesn't wrap the real Forge CLI, so runtime behavior is unaffected.
- However, any docs, skill text, or error messages that reference the old
forge webtrigger root-command usage for obtaining URLs are now stale and should point at forge webtrigger create instead.
- Worth a quick grep of docs/README/skill content for
forge webtrigger to confirm nothing tells users to run the removed root form.
Link: https://developer.atlassian.com/platform/forge/changelog/#CHANGE-3422
GUID: CHANGE-3422
Published: Wed, 16 Sep 2026 01:16:18 GMT
Category: Announcement
What's changing
Atlassian has removed support for the bare
forge webtriggerroot command for creating web trigger URLs; the deprecation window has passed. The command now requires an explicit sub-command. To create a web trigger URL via the CLI you must use:Running the root command to generate a URL no longer works.
Parity impact for forge-sim
Simulator area: web triggers / CLI local-dev semantics.
forge_fire_web_trigger, the dev server/__trigger/<key>endpoint) doesn't wrap the real Forge CLI, so runtime behavior is unaffected.forge webtriggerroot-command usage for obtaining URLs are now stale and should point atforge webtrigger createinstead.forge webtriggerto confirm nothing tells users to run the removed root form.Link: https://developer.atlassian.com/platform/forge/changelog/#CHANGE-3422