Preparing for Confluence 7.13

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

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 milestone
7 June 2021

7.13.0-m09

Download
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

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. 

Upcoming security uplift

Status: ADVANCE NOTICE

We'll be identifying and upgrading core components and libraries to the newest versions. We will not break our official APIs. However, certain libraries, transitive dependencies, and behaviours might change. We'll list information about upgraded dependencies and libraries in this EAP documentation.

Hibernate upgrade

Status: ADVANCE NOTICE

We're working on upgrading Hibernate from 5.2 to 5.4. This includes breaking changes like removing deprecated features/interfaces.

Notable features that have been removed:

  • Support for JDBC parameterised queries. Classes that implement HibernateContentQueryFactory should be verified to assure that named parameters are used instead.
  • RegionAccessStrategy and other access strategy interfaces have been replaced.

See Hibernate 5.2 to 5.4 upgrade contains breaking changes for more information. We are targeting Confluence 7.14 for this upgrade.

Removal of editor-v3 

Status: ADVANCE NOTICE

When we upgraded our editor to TinyMCE v4 way back in Confluence 6.14, we introduced an unsupported dark feature that could be used to revert to the v3 editor (frontend.editor.v4 / frontend.editor.v4.disable). We plan to remove this dark feature flag in a future Confluence release, as they are no longer tested or reliable.

Once that happens, the editor-v3 WRM context will no longer be loaded. Any resources used only in this context can be removed completely. The editor and editor-v4 contexts are unchanged, and with this change, resources in editor-v4 can be safely moved to editor.

Changes to basic authentication

Status: IN PROGRESS

We plan to provide admins the ability to disable basic authentication, and will be recommending any integrations use personal access tokens instead. Learn more about disabling basic authentication. This change won't be in 7.13, but you can start testing now by manually upgrading the SSO for Atlassian Server and Data Center to 4.2.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 7 - 7 June 2021

Milestone 7.13.0-m09

No significant changes in this milestone.

EAP 6 - 31 May 2021

Milestone 7.13.0-m08

No significant changes in this milestone.

EAP 5 - 25 May 2021

Milestone 7.13.0-m07

No significant changes in this milestone.

EAP 4 - 17 May 2021

Milestone 7.13.0-m06

No significant changes in this milestone.

EAP 3 – 3 May 2021

Milestone 7.13.0-m04

No significant changes in this milestone.

EAP 2 – 26 April 2021

Milestone 7.13.0-m03

No significant changes in this milestone.

EAP 1 – 19 April 2021

Milestone 7.13.0-m02

No significant changes in this milestone.


Looking for updated documentation? Check out the Confluence EAP space for the latest docs.

Did you know we’ve got a new developer community? Head to community.developer.atlassian.com/ to check it out! We’ll be posting in the announcements category if when new EAP releases are available.

Last modified on Jun 7, 2021

Was this helpful?

Yes
No
Provide feedback about this article
Powered by Confluence and Scroll Viewport.