Confluence 7.13 is a Long Term Support release, so we’re not including any new features or significant changes. This release is focused on bug fixes to support our largest customers.
Many customers on Confluence 6.13 and 7.4, our last Long Term Support releases, have been eagerly awaiting this Long Term Support release, and we are expecting a lot of upgrades to this version. So check out our Preparing for Confluence 7.13 guide, start your testing, and remember to mark your app as compatible as soon as you can after release day.
Get started
Download the beta from our site to start testing your app for compatibility with the changes. Be sure to take a look at our Preparing for Confluence 7.13 guide to find out what you need to do to make your app compatible. We’ll update that page regularly, so keep an eye on it to see any changes.
For folks who are using docker images to keep their EAP server up to date with the latest: Confluence 7.13 beta is in included in the ‘eap’ label: Docker
I just verified that by refreshing my image that is configured to use the ‘eap’ label like this in docker-compose.yml:
Thanks @christoffer. Too many years of releasing betas, I was obviously on autopilot and missed that it had been named differently this time. I’ve updated the references in the doc.
Glad the docker tag is working as expected @TureHoefner. The intention is that the latest EAP be included in that label (including beta, and hopefully next week release candidate).
NOTE : This Docker image is published as both atlassian/confluence and atlassian/confluence-server. These are the same image, but the -server version is deprecated and only kept for backwards-compatibility; for new installations it is recommended to use the shorter name.
Hi Jens, sorry I’ve only just seen your message, and am following with the dev team. I’m not directly involved in getting the releases on dockerhub, but I’ll chase up what has gone wrong (again).
The problem should have been resolved fairly soon after your original comment (sorry for the delay). There was a problem with some of our automation, but it is apparently fixed now.