Contents of the release
-
Removal of Indexing v1. Administrators It was introduced in 3.5, made mandatory in 4.0 for Data Center customers, introduced tools to compare and migrate. We’re finally making it mandatory in 4.7. See https://docs.requirementyogi.com/data-center/choosing-the-indexing-engine and child pages if it is a concern for you.
-
New EULA. Administrators Our EULAs specify that upgrading constitutes an approval. Although this is a usual practice on the Atlassian Marketplace and on paar with most large and small vendors, legal services often doubt the validity of EULAs when active acknowledgement is not performed. To make it explicit, we’ve added a warning to administrators in 4.6, and made it mandatory in 4.7. Upon installation, administrators will be required to confirm their approval to the new EULA, with a 45-day grace period.
-
Guidelines for LLMs. We’ve introducing a new idea and testing customer feedback on it. We’re introducing user sessions, where users define a scope, and the LLM must use an additional header on top of Confluence authentication and permissions.. If enabled, our REST API will reject requests outside of the defined scope. The feature is described on README for LLMs in Data Center and initially developed in RY-2109.
-
Compatibility with Confluence 11.0: Great news, Atlassian has published Confluence 11 with very good backwards-compatibility, therefore we were able to enable compatibility with both 10 and 11 with minimal changes from the customer perspective.
Bugfixes and minor features
-
RY-2102 In the renaming of requirements, we used to process all pages of spaces, it was a bug. We are now searching only for pages containing this requirement key. We are also ignoring pages which cannot be updated.
Notes for system administrators
-
Confluence 9.2 is not supported by this release.
-
Confluence 9.2 will be supported by the previous branch, 4.6.x, until December 2026, to align with Atlassian’s long-term support releases. See Compatibility matrix.
-
As said above, indexing v1 is removed and the EULA dialog must be confirmed.
Risk assessment
Low We don’t foresee any risk in upgrading.