This page includes release notes, links to product release notes, and updates for Confluence. Use this page to keep track of upcoming changes, deprecation notices, new features, and feature updates.
A Confluence 11.0 EAP milestone is available now for testing. To find out what’s changed, check out Preparing for Confluence 11.0.
Got feedback or want to discuss the latest EAP? Chat with us in this Atlassian Developer Community thread. The earlier we know about potential problems, the more time we'll have to fix them before the final release.
We are upgrading from jQuery 3 to 4 in Jira 12, Confluence 11, Bitbucket 11, Bamboo 13, and Crowd 8. jQuery migrate will also be removed. Much frontend code depends on jQuery and we expect this will require upgrade work in apps (e.g. P2 plugins) and custom integrations with a frontend.
We consider this a breaking change and thus do not plan to backport to existing LTS releases.
This is to continue to meet customers' demands for secure & compliant products. We must be proactive in this upgrade because of how much our products and apps depend on it. We had many requests in the past to upgrade from jQuery 2 to 3, especially when there were vulnerabilities found in jQuery.
As we learn more and refine developer tooling to assist with the work, we will update the developer documentation
Many of the changes can be prepared for in a way that's backwards compatible with v3 so as many (compatible) changes as possible will also be backported to the LTS versions of Jira (11.3), Confluence (10.2), Bamboo (12.1) and to the latest versions of Bitbucket 10 and Crowd 7. The intention is to make it easier to test your app without having to worry about unrelated breaking changes.
Similarly, AUI 10.1 adds support for jQuery 4.
We will continue to provide jQuery web-resources and we ask developers to use them so that if needed we can roll out security patches as quickly as possible.
We are still early on in upgrading the Data Center products themselves. Future EAP versions will come with jQuery 4, but this might not arrive in the first few versions.
We have not currently noticed any JS behaviour nor signature changes that would affect apps. Please let us know if you spot something, and we will document it.
See the developer community announcement topic for more information and to leave feedback
Data Center products support React 18 starting with the following versions:
Bamboo 12.0
Bitbucket 10.1
Confluence 10.1
Crowd 7.1
Jira Software 11.2
Jira Service Management does not bundle on its own copy
React 18.3.1 is provided by a bundled com.atlassian.plugins.react cross-product app that supersedes previous product specific React web-resources. React dependencies are exposed as AMD modules via the following web-resources:
com.atlassian.plugins.react:react-core-amd provides the atlassian/libs/react AMD module
com.atlassian.plugins.react:react-dom-amd provides the atlassian/libs/react-dom and atlassian/libs/react-dom/client AMD modules
com.atlassian.plugins.react:react-amd is a convenience bundle of React and ReactDOM above
Where applicable, existing React 16 web-resources are considered deprecated and will be removed in the next platform releases.
Additionally, we plan to upgrade to React 19 following the Atlaskit support as announced in https://community.developer.atlassian.com/t/rfc-78-dropping-support-for-react-16-and-rendering-in-a-react-18-concurrent-root-in-jira-and-confluence/87026/23
What’s new in Confluence Data Center 10.2 LTS?
10.2 is a Long Term Support release. More about Long Term Support Releases
Performance benchmarking report
Search and WebDAV strict patch settings limited to system admins
Cloud connectors for hybrid integrations
To explore 10.2, see Confluence 10.2 Release Notes.
Starting with the following versions, major product releases will no longer support installing plugins that require transformation:
Confluence 11.0
Jira Software 12.0
Jira Service Management 12.0
Bamboo 13.0
Bitbucket 11.0
Crowd 8.0
For details, explore Transformed to transformerless plugin conversion.
Context:
Any P2 plugin development using modern versions of Atlaskit will end up compiled-css.css files inside target/classes. We’ve been upgrading React & Atlaskit in the DC products and so many of the P2 plugins that make up our products now have a compiled-css.css file.
This made a long-standing bug with local development more obvious. The first compiled-css.css file found by the plugin system was used for all P2 plugins (instead of using the specific file from the respective plugin). https://compiledcssinjs.com/ compiles equivalent styles to the same CSS classname and there is decent, but not perfect overlap in styles. The result was that often just one Atlaskit component wouldn’t render correctly or any plugin-specific styles would be missing. This can be quite hard to debug because in the browser development tools it looks like the compiled-css.css file doesn’t change no matter what you do, this is of course because it’s using another plugins'.
Action:
We have fixed this long-standing underlying bug, but remained backwards compatible. To use the new, fixed local development system instead of the existing, buggy implementation you will need to use the upcoming post-2025-LTS product versions for local development (e.g. Confluence 10.3, e.g. Jira 11.4), and also upgrade QuickReload to 6.2.0+ (included in AMPS 9.7.2). If everything goes smoothly we will consider backporting to LTS releases of the products. Note: Crowd doesn’t have LTS releases, but it’s looking to be in Crowd 7.3
For more details read the original bug report: https://ecosystem.atlassian.net/browse/PLUG-981.
If you have any issues or questions, feel free to ask us on developer community.
Cheers,
Michael Kemp
A Confluence 10.2 beta version is available now for testing. To find out what’s changed, check out Confluence 10.2 beta release notes. This time, there are no Early Access Programs (EAPs) releases. Instead, only beta releases are available. This is because Confluence 10.2 is a Long Term Support (LTS) release.
Got feedback or want to discuss this beta? Chat with us in this Atlassian Developer Community thread. The earlier we know about potential problems, the more time we'll have to fix them before the final release.
We’re sharing a guide that explains the benefits of using OpenSearch as an alternative to the default Lucene search platform in Confluence Data Center.
It covers:
Key differences between OpenSearch and Lucene
Benchmark results that show OpenSearch delivers faster search and better scalability
Guidance on when and why to switch, with further configuration steps
Explore the full documentation for more details and performance test results
What’s new in Confluence 10.1?
Find and sort most used macros in your site
Manage your integrations and automations with service accounts
Connect securely with OAuth 2.0 for app links
Upgrade to React 18.3 and latest Atlaskit
Editor upgrade to TinyMCE 7.9.1
Lots more!
To learn more, see Confluence 10.1 release notes.
A Confluence 10.1 beta version is available now for testing. To find out what’s changed, check out Confluence 10.1 beta release notes.
Got feedback or want to discuss this beta? Chat with us in this Atlassian Developer Community thread. The earlier we know about potential problems, the more time we'll have to fix them before the final release.
Trusted apps authentication has been removed. For details, see Removal of Trusted apps.
A supported migration path is available via OAuth 1 with impersonation.
Details
OAuth 1 with impersonation allows plugins to generate signed HTTP requests back to the same Data Center instance while impersonating a specific user.
Relevant ticket: CONFSERVER-99078 – Java API for authenticated HTTP requests to current Confluence instance.
A demo plugin illustrates how to implement OAuth 1 with impersonation for both Jira and Confluence: https://bitbucket.org/atlassian/dc-platform/src/4407b6ea004529ba93a69315d99765657ce7829b/demos/oauth1-impersonation-plugin-example/?at=release%2F8.0.x.
OAuth 1 with impersonation is already part of the existing OAuth 1 plugin.
Product Changes
Jira 11.0.1 (released) and Confluence 10.0.4 (scheduled for release) now automatically create a host consumer provider on the product side, enabling plugins to connect back to the same Data Center instance.
A Confluence 10.1 EAP milestone is available now for testing. To find out what’s changed, check out Preparing for Confluence 10.1.
Got feedback or want to discuss the latest EAP? Chat with us in this Atlassian Developer Community thread. The earlier we know about potential problems, the more time we'll have to fix them before the final release.
What’s new in Confluence 10.0?
Spring and Jakarta upgrade
Removal of deprecated components in AUI 10
End of support for LESS
Removal of Trusted apps
End of support for the Original theme
Global serialization filter
App signing is now enabled by default for app installations
Enhanced security with Content Security Policy
Basic authentication disabled by default
Monitoring and observability of the Synchrony process
Add scopes to REST endpoints to use OAuth 2.0 2LO
Control how many labels display in macros
Lots more!
To learn more, see Confluence 10.0 release notes.
This release doesn’t support Server licenses. If you have a Server license, check out your options for upgrading.
A Confluence 10.0 beta 3 version is available now for testing. To find out what’s changed, check out Confluence 10.0 beta release notes.
Got feedback or want to discuss this beta? Chat with us in this Atlassian Developer Community thread. The earlier we know about potential problems, the more time we'll have to fix them before the final release.
A Confluence 10.0 beta version is available now for testing. To find out what’s changed, check out Confluence 10.0 beta release notes.
Got feedback or want to discuss this beta? Chat with us in this Atlassian Developer Community thread. The earlier we know about potential problems, the more time we'll have to fix them before the final release.
Rate this page: