Confluence 8.9 upgrade notes

Here are some important notes on upgrading to Confluence 8.9. For details of the new features and improvements in this release, see the Confluence 8.9 release notes.



Upgrade notes

Possible port conflict with Hazelcast upgrade

This release contains an upgrade to Hazelcast IMDG 5.3.6. This recent upgrade enhances our platform by improving JMX metrics for more efficient garbage collector operations, and optimized memory consumption. This version does not support rolling upgrades (ZDU).

Some customers who use Windows may experience a conflict between Confluence and Active Directory (dns.exe) both trying to use port 54327. If this happens, exclude the port from the port range.

Follow the steps on our troubleshooting page for full details.

Updated editor color palettes

In preparation for the release of dark theme, we’ve updated the text color and table cell background color palettes to use design tokens. These updated palettes now use colors that also improve accessibility contrast.

As a result of this change, once dark theme is released in the coming months, all colors in the editor will be converted to match the updated color palettes. That means you will no longer be able to customize these palettes using the temporary workaround.

Advance notice: take a peek!

OpenSearch opt-in feature ready for early access

We’re working to introduce OpenSearch as an opt-in search engine in an upcoming feature release of Confluence 9.x. It will not be part of Confluence 9.0. This will provide more advanced indexing options leading to less processing requirements and faster search results.

As part of our Early Access Program (EAP), we’ve updated the OpenSearch upgrade guide, to include links to new content on how to set up OpenSearch, and information on what's currently working and what we're still working on, should you wish to test during the EAP phase. At this early stage, OpenSearch during EAP is not suitable for production environments, but we invite you to try it on your testing environment.

Contact us on osfc@atlassian.com, or via our customer support channel.

Dark theme for Confluence

As we’re approaching the release of dark theme in Confluence 9.0, you can now get a first glimpse by enabling the theme.switcher dark feature. Bear in mind that we’re still working on finishing touches before the official release, and switching on the dark feature will enable dark theme for all users. We encourage you to try it in your staging environment, and let us know your feedback here.

Get ready for Confluence 9.0

We’re working on a major platform release with Confluence 9.0, due to be released mid year. Confluence 9.0 will have a number of upgrades. For early information, visit our Preparing for Confluence 9.0 page.

Supported platforms changes

End of support for PostgreSQL 12

As previously announced, PostgreSQL 12 is no longer supported.

End of support announcements.

Advance Notice: End of support for Java 11

  • Confluence 8.9 will be the last release to support Java 11.
  • Java 11 will not be supported in Confluence 9.0 and later versions.

For more information on these notices, see our End of Support Announcements for Confluence.

Changes to Security Bug Fix Policy

We’ve updated the Atlassian Security Bug Fix Policy. Changes took effect across all Data Center products on March 15, 2024. Previously, we delivered bug fix releases for any supported Long Term Support release in accordance with the Atlassian Support End-of-Life Policy, and for all product versions that are no older than 6 months.

With our new policy, we will continue to deliver a bug fix release for any supported Long Term Support release in accordance with the Atlassian Support End-of-Life Policy, but we are updating our policy to only support the most recently shipped feature release.


More info

In the event of a critical vulnerability, we will take all of the following steps:

  1. Ship a bug fix for the latest feature release of the product affected by the vulnerability.

  2. Ship a new feature release for the affected product according to the release schedule.

  3. Ship a bug fix release for all supported Long Term Support releases of the affected product, adhering to the Atlassian Support End of Life Policy.

We aim to develop the most effective methods for enhancing the security of our software and delivering updates faster and more frequently. When considering an upgrade, you can be sure that the latest feature release is the most secure and stable product version as it contains the most up-to-date security fixes and feature enhancements.

If you have any concerns or if you require clarification on any aspect of the updated bug fix policy, please do not hesitate to reach out to our support team.

Find more details of the new process at Announcement: Planned changes to the Security Bug Fix Policy | Atlassian Support | Atlassian Documentation

Infrastructure changes 

Head to Preparing for Confluence 8.9 to find out more about changes under the hood. 

Known issues

If you encounter a problem during the upgrade and can't solve it, please create a support ticket and one of our support engineers will help you.

Upgrade procedure

Always test the upgrade in a test environment before upgrading in production.

To upgrade Confluence to the latest version:

  1. Go to Administration  > General Configuration > Plan your upgrade and select the version you want to upgrade to. This will run the pre-upgrade checks.
  2. Go to Administration  > General Configuration > Troubleshooting and support tools to check your license validity, application server, database setup, and more.
  3. If your version of Confluence is more than one version behind, read the release notes and upgrade guides  for all releases between your version and the latest version.
  4. Back up your installation directory, home directory, and database.
  5. Download the latest version of Confluence.
  6. Follow the instructions in the Upgrade Guide.

Update configuration files after upgrading

The contents of configuration files such as server.xml, web.xml , setenv.bat / setenv.sh, and confluenceinit.properties change from time to time. 

When upgrading, we recommend manually reapplying any additions to these files (such as proxy configuration, datasource, JVM parameters) rather than simply overwriting the file with the file from your previous installation; otherwise you will miss out on any improvements we have made.

Last modified on Apr 10, 2024

Was this helpful?

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