ST-2026-247 · SDKs & toolchains
Atlassian removes the root Forge CLI webtrigger command
Atlassian removed support for using the root forge webtrigger command to create URLs after its deprecation window, requiring the forge webtrigger create sub-command instead.
Previous state
Developers could use the root forge webtrigger command to generate a Forge web trigger URL during the deprecation window.
Current state
The root forge webtrigger command no longer generates a URL; developers must use forge webtrigger create, optionally with --functionKey.
Affected users
Who needs to care
Forge app developers and automation that still invoke the root forge webtrigger command to create web trigger URLs.
Required response
What to do
Replace root-command invocations with forge webtrigger create, add --functionKey where non-interactive selection is required, and test affected scripts against the current Forge CLI.
Evidence boundary
What the source does not prove
Atlassian proves removal of the root URL-generation command and the supported create sub-command. It does not remove Forge webtriggers generally, the list command, or the webtrigger lifecycle APIs.
Lifecycle history
Dated event sequence
- Root command support removed
Atlassian stated that the deprecation window had passed and the root forge webtrigger command no longer creates web trigger URLs.
- SchemaTrace verification
The official Forge changelog continued to require forge webtrigger create as the supported replacement.
Evidence ledger
First-party sources
- 01Atlassian Developer — Forge changelog — Remove deprecated forge webtrigger root command
Official Forge CLI lifecycle and replacement-command authority · 2026-09-14
Open official source ↗