This documentation is intended for Confluence developers who want to ensure that their existing plugins and apps are compatible with Confluence 11.0.

Watch this page to find out when a new milestone is available and what’s changed. We will publish formal release notes once we release a beta.

Latest milestones

Issues with this milestone?

Hit the Feedback button on the Confluence EAP header or raise an issue to tell us about it.

On this page:

• Planned changes
• Implemented changes

Planned changes

In this section we'll provide an overview of the changes we intend to make, so you can start thinking how it might impact your app. We'll indicate when a change has been implemented, and in which milestone. 

Custom HTML editing now disabled by default

Status: DONE

To improve security, editing custom HTML is now disabled by default. If you need to enable custom HTML, set the confluence.custom.html.config.enabled system property to true. Only system administrators can enable this feature.

How to configure system properties

Look and Feel layouts editing now disabled by default

Status: DONE

To improve security, configuring Look and Feel layouts is now disabled by default. Admins can only view existing layout configurations. To enable layout editing, set the confluence.site.layout.edit.enabled system property to true. Only system administrators can enable this feature.

How to configure system properties

Removal of support for transformed plugins

Status: IN PROGRESS

We are deleting all transformation code and infrastructure from the platform. This means the runtime transformation process, which previously converted older plugin formats at startup, will no longer exist.

If a user attempts to install or enable a transformed plugin, the UPM will block the action and display a clear error message. Any transformed plugins already installed will be forcibly disabled upon upgrading to a Platform 9-based product version.

To ensure your apps continue to work on Data Center Platform 9, you must migrate them to the "transformerless" format.

We provide a conversion script to help automate this process. For further guidance and best practices, you can refer to our documentation on Spring Java configuration of app components.

Complete removal of OpenSymphony PropertySet

Status: IN PROGRESS

The following APIs that leverage PropertySet were made read-only in Confluence 10.0. They have been permanently removed in Confluence 11.0.

• com.atlassian.confluence.user.ConfluenceUserPropertySetFactory

• com.atlassian.confluence.user.UserAccessor#getPropertySet

• com.atlassian.confluence.core.ConfluencePropertySetManager

Complete removal of Bandana and XStream

Status: IN PROGRESS

After making Bandana read-only in Confluence 10.0, we will remove Bandana entirely in Confluence 11.0. For security reasons, Confluence 11.0 will also no longer bundle the XStream library.

The following packages will be removed and will no longer be available to plugins:

• com.atlassian.bandana*
• com.atlassian.confluence.setup.bandana*
• com.atlassian.confluence.setup.xstream*
• com.thoughtworks.xstream*

Direct access to the Bandana database table will no longer be possible in Confluence 11.0.

Apps that currently use Bandana must migrate to alternative storage (for example, Active Objects or SAL Plugin Settings) before upgrading to 11.0.

For more information, go to Preparing for Confluence 10.0.

Implemented changes

In this section we'll provide details of changes we have implemented, organised by the milestone they are first available in. This will help you decide which milestone to use when testing.

EAP 02 – 3 March 2026

Milestone 11.0.0-m79

Contains:

• Look and Feel layouts editing now disabled by default
• Minor bug fixes

EAP 01 – 10 February 2026

Milestone 11.0.0-m55

Contains:

• Custom HTML editing now disabled by default
• Minor bug fixes