This page includes release notes and updates for Confluence Cloud app developers. Use this page to keep track of upcoming changes, deprecation notices, new features, and feature updates from Confluence Cloud.
For updates about changes to the Forge platform, see the Forge changelog in the Forge documentation.
You can also ask questions and learn from other Confluence Cloud developers on the Atlassian Developer Community.
As part of the Atlassian visual refresh updates, we updated the UI Kit Icon component. Some glyphs get a new look, and many more glyphs have been added. There are also a number of deprecations, as detailed below.
The size prop will only support the values "small" and "medium". The value "large" is now deprecated and will be removed.
The prop primaryColor has been renamed to color.
The prop secondaryColor is now deprecated and will be removed.
Some glyphs haven been replaced and others will be removed. Visit the Icon migration guide for information on finding a replacement.
The new default size for icons will change from 24x24 pixels to 16x16 pixels.
All deprecations and breaking changes will take place on Jan 1, 2026. Until then, the new Icon component will be fully backwards-compatible. Any deprecation will trigger a console warning prefixed with [@forge/react: Icon] on non-production environments.
We’ve added a set of new Confluence product events to track content changes and permission updates across Confluence. Forge apps can subscribe to them to be invoked when:
a page, blogpost, or attachment is trashed or restored
custom content is created, updated, trashed, or restored
a comment is deleted
restrictions or permissions are updated
avi:confluence:trashed:page
avi:confluence:restored:page
avi:confluence:trashed:blogpost
avi:confluence:restored:blogpost
avi:confluence:created:custom_content
avi:confluence:updated:custom_content
avi:confluence:trashed:custom_content
avi:confluence:restored:custom_content
avi:confluence:trashed:attachment
avi:confluence:restored:attachment
avi:confluence:deleted:comment
avi:confluence:permissions_updated:page
avi:confluence:permissions_updated:blogpost
avi:confluence:permissions_updated:whiteboard
avi:confluence:permissions_updated:database
avi:confluence:permissions_updated:folder
avi:confluence:permissions_updated:custom_content
avi:confluence:permissions_updated:space:V2
See more details about these events here: https://developer.atlassian.com/platform/forge/events-reference/confluence/
We have introduced the ability to define content property indexing via a new Forge Confluence content property module. This makes the data inside content properties available to CQL search, allowing apps to use CQL to search for content they've set data on using the propertyKey or its searchAlias.
Content properties allow you to store key-value pairs against a piece of content. Each value must be well-formed JSON.
When defined as part of a content property module, values from these JSON objects can be extracted, indexed, and made available to CQL queries.
Content properties can be set against multiple Confluence content types via the Content properties REST APIs.
Forge Remotes are now available in the Atlassian Government Cloud. Please refer to the AGC documentation for details on supporting Forge Remotes within your AGC Forge app.
We are deprecating the following Atlassian Connect-related unscoped npm packages in favor of their @atlassian scoped equivalents.
Starting 24th of July 2025, these packages will no longer be supported, and we recommend transitioning to the corresponding scoped packages instead.
The affected packages are:
old package name | new package name | latest version of new package |
|---|---|---|
|
|
The scoped packages maintain 100% API compatibility with their unscoped versions, ensuring a seamless migration experience. We recommend updating to the scoped versions as soon as possible before the deprecation date.
All of these packages are part of the Atlassian Connect ecosystem and are used for developing Connect apps. The scoped packages provide identical functionality but align with our standardized package naming conventions. This change helps ensure consistency across our npm ecosystem and improves package security.
To update your dependencies, replace the unscoped package names with their scoped equivalents in your package.json files.
If you encounter any issues during migration, please reach out through the Developer Community forums.
We’re introducing the ability for apps to publish events, allowing for enhanced interoperability between apps. This feature enables apps to subscribe to events using the existing https://developer.atlassian.com/platform/forge/manifest-reference/modules/trigger/ module, opening up new possibilities for app interactions.
Developers can start using app events by implementing the https://developer.atlassian.com/platform/forge/manifest-reference/modules/event/ module in their apps. For detailed guidance and examples, refer to https://developer.atlassian.com/platform/forge/events-reference/app-events/.
To publish events using the runtime API, you need at least version 2.0.0 of the @forge/events dependency. Add this to your package.json:
1
2
3
4
5
{
"dependencies": {
"@forge/events": "^2.0.0"
}
}A new getUrl method has been added to router in @forge/bridge. The method will accept a NavigationLocation object and return a URL object for the corresponding destination.
This method is in Preview. For more details, see the router documentation.
Run npm install --save @forge/bridge@latest in your resource directory to install the latest version of Forge bridge.
We've added an openOnInsert parameter for macros with classic configuration. This parameter allows you to control whether the configuration panel is automatically opened on macro insert, enhancing the user experience by providing more flexibility.
To use this feature, you must be on the latest @forge/cli version 11.6.0. For more information, see the macro module documentation.
Atlassian Team entities are now able to be modified via many existing Group APIs if a Team ID is passed instead of a Group ID. They will not be returned in search or lookup results. They can be fetched and modified by ID.
Rollout: Progressive rollout by tenant in progress
This will be visible from Cloud Admin APIs immediately after rollout. Jira and Confluence APIs will take longer to roll out.
Blob objects can now be sent and received via the events API. This enhancement allows for more efficient data handling and transmission within the API.
Update to the latest version of @forge/bridge with npm install --save @forge/bridge@latest
On February 10th 2025, we announced the Deprecation of automation.atlassian.com incoming webhooks for Automation rules https://developer.atlassian.com/changelog/#CHANGE-2299. As of 30 May 2025, the legacy incoming webhook has now been deprecated.
We’ve started to gradually shut down the legacy endpoint across all customer sites. Rules recently triggered through legacy webhooks will now be marked with error icons.
To view impacted rules:
Open the automation rule list in Jira or Confluence.
Click on the ‘Trigger' filter and select the ‘Incoming webhook’ filter. All rules triggered by an incoming webhook will be shown.
Within these filtered rules, any which have recently been triggered through a legacy webhook will have a error icon next to their name. This shows which rules were unable to complete a successful run due to using the legacy URL.
To learn how to update these rules, you can read our support documentation.
Since incoming webhooks may be called from non-Atlassian systems that we don’t have access to, or aren’t aware of, rule owners will need to migrate impacted rules to the new endpoint manually, read our support documentation.
Atlassian font assets are now being preloaded by the Connect JS library (ACJS) to support consistent typography across Atlassian and Connect apps. These assets are served from dedicated design system CDN https://ds-cdn.prod-east.frontend.public.atl-paas.net.
Connect apps using the standard all.js ACJS bundle will now automatically pre-load:
atlassian-fonts.css
Atlassian Sans font files (e.g., AtlassianSans-latin.woff2)
These files are delivered from the new ds-cdn host. The change was previously gated and is now enabled for all Connect apps.
Apps with a strict Content Security Policy (CSP) must update their style-src and font-src directives to allow the new CDN host. Without this, CSP violations may block font and styles loading.
Update your CSP to include:
1
2
style-src https://ds-cdn.prod-east.frontend.public.atl-paas.net
font-src https://ds-cdn.prod-east.frontend.public.atl-paas.net This change improves visual alignment with Atlassian’s visual refresh program. For further background, see:
We’ve added new Confluence product events for labels:
avi:confluence:created:label
avi:confluence:added:label
avi:confluence:removed:label
avi:confluence:deleted:label
You can use these events to invoke your Forge app function when label is created, added to an entity, removed from an entity, or deleted. For more details see https://developer.atlassian.com/platform/forge/events-reference/confluence/#labels.
With the Forge CLI 11.5.0 release, we've enhanced the Forge platform to let you specify the memory available to functions at runtime by setting the memoryMB property in the Manifest (https://developer.atlassian.com/platform/forge/manifest-reference/#runtimev2) . Increasing the function memory also increases its CPU allocation. The memory value can now be set between 128 MB and 1,024 MB, doubling the previous limit of 512 MB. If you do not configure the function memory, the default memory allocation of 512MB applies to your function. This change helps address out-of-memory (OOM) issues by allowing higher memory allocation.
For more information on configuring Forge function memory, see https://developer.atlassian.com/platform/forge/manifest-reference/#runtimev2.
For details on the relationship between memory and CPU allocation, refer to the https://docs.aws.amazon.com/lambda/latest/dg/configuration-memory.html.
We’ve released a new module, Confluence page banner, which enables apps to add a banner to Confluence pages. This module is generally available.
This feature provides equivalent Forge functionality to the Connect Confluence atl.general web panel.
Rate this page: