Khoros Communities - Updated Release Process
To improve your experience and simplify our release process, we are updating how we handle Khoros Communities releases. This process will start to apply from Communities Release 25.09. What's Changing Communities will have two types of releases going ahead - Standard releases and Patch releases Standard releases are regular releases that will happen on a cadence during Maintenance Windows. All releases will be standard releases Patch releases are critical bug fixes or security fixes, which happen out-of-band During Standard releases, our teams will automatically upgrade customers on the latest release providing windows for feedback Customers can reach out to support for upgrading legacy instances or for any other feedback Standard Releases We will have a standardized release process for both Aurora and Classic. In a standard release, we will auto-upgrade customers on the latest release. These releases will include features and non-critical bugs. Version numbers for the standard release will follow the existing version numbers. However, we will no longer be treating releases as major or minor - we will treat every release as a standard release. The process will begin when we publish the release notes. The release notes will announce the plan and scope of an upcoming release. After we post the release notes , customers will be notified and have a week to provide feedback to their Customer Representatives on the upcoming release. After this one week, we will upgrade the stage environments. We will open a two-week testing window, where customers can test on their stage environments and provide feedback. Again, Customer Representatives will be the points of contact during this phase. At the end of the two-week window, we will perform the upgrade in production for customers whose stage environments we have successfully upgraded and do not have any open feedback. For both stage and production, we will use existing Maintenance windows, as we expect downtime. If you are on an older version and want to opt back into auto-upgrades, please reach out to your Customer Representative. They can upgrade you to the latest version at any time Patch Releases We will release patches out-of-band for critical bugs that affect multiple customers or affect a release's stability, and security and vulnerability fixes. We will apply patch releases for all customers on the latest version, given that these are critical in nature. Our team will publish the release notes, notify customers and apply patches in a three-day window. Customer Representatives will handle any customer feedback during this phase. Version numbering for patch releases will follow <standard release version number>.<number>, where number will be incremented for each patch and reset after a particular standard version. As an example, the first patch after 25.8 will be numbered 25.8.1, the second patch as 25.8.2 and so on. However, the first patch applied after 25.9 will be 25.9.1. We will use Change windows for non-downtime needs and maintenance windows timeslots for downtime needs. Customer support will notify customers about downtime needs. Customer representatives will reach out if a patch applies to a Customer on an older version. As always, Customer Representatives are available for any feedback. What to expect next As we stabilize and based on feedback on the new release process, we will also be reviewing the cadence of releases which is right now monthly. The intent is to provide high quality releases, minimizing customer disruptions, and allowing customers time to provide feedback and adjust.
Khoros Communities 25.09 - Release Notes
The Khoros Communities 25.09 release includes performance improvements, stability enhancements, and bug fixes across search, caching, authentication, and moderation features. Classic Fixed inbox search not returning results for partial word matches. Fixed an issue where the private notes page would error when performing an empty search. Fixed image URLs not being indexable by search engines due to incorrect robot headers. Fixed an issue where Salesforce user ranks were not updating after the initial sync. Fixed archive dashboard totals showing incorrect counts due to deleted boards being included. Fixed delete confirmation errors preventing content deletion. Fixed event pages showing errors after creating and publishing new events with optional livestream details. Aurora Fixed an issue where Salesforce user ranks were not updating after the initial sync. Fixed archive dashboard totals showing incorrect counts due to deleted boards being included. Fixed an error that occurred when viewing analytics for occasion reply messages. Fixed unread and view counts not updating without a page refresh. Fixed inbox search not returning results for partial word matches. Fixed an issue where the private notes page would error when performing an empty search. Fixed image URLs not being indexable by search engines due to incorrect robot headers. Fixed an authentication issue where cookies were not being properly echoed during login/logout flows. Fixed an issue where session cookies were being incorrectly cached for anonymous users. Improved page caching performance by moving from memory-based to filesystem-based storage. Fixed a page caching issue that was reusing parent frame IDs across different users. Fixed the 3-dot action menu not working properly in text key mode within Manage Content. Fixed the 3-dot action menu not appearing for reported private messages in Manage Abuse. Fixed message action menus not responding consistently across different content types. Fixed message preview pages reloading endlessly and preventing user actions. Fixed duplicate replies being created when responding to messages at deeper thread levels. Fixed pagination issues with archived messages where the cursor was not advancing properly. Fixed a null pointer exception occurring when deleting articles via API. Fixed an issue where followers were not consistently receiving edit notifications according to their preferences. Fixed subscribers receiving unnecessary emails for non-publish workflow actions. Fixed an infinite initialization loop occurring in SDK preview for custom components. Fixed an issue where component assets were not loading correctly when switching branches. Fixed database errors caused by custom field metadata keys exceeding the allowed size limit. Fixed an issue where pasted email addresses were being replaced with suggested users when pressing Enter in group/event invites. Fixed delete confirmation errors preventing content deletion. Fixed event pages showing errors after creating and publishing new events with optional livestream details. Staging and Pre-Prod rollout: September 15 Production rollout: September 29 The rollout will follow the standard maintenance windowsKhoros Communities 25.08 - Release Notes
The Khoros Communities 25.08 release includes several important security improvements and bug fixes. [Classic] Fixed a cross-site scripting (XSS) vulnerability affecting embedded YouTube videos on community pages. [Aurora] Certain specific custom access permissions was blocking user registration, due to attempting to verify permissions before the user was registered. This has been addressed so that permissions are checked in the correct sequence. [Aurora] Fixed an issue where users were unable to join Zoom meetings when registration was set to "required"; users would instead see an error message. [Aurora] Fixed an issue with headers and footers appearing multiple times on some community pages. [Aurora] Addressed an Aurora GraphQL API issue where certain custom fields were omitted from responses. These values now appear correctly. [Aurora] Resolved an issue where the "CurrentUser" endpoint returned information about the anonymous user, not the actual current user, when using the Authorization header method of authentication. Release Date: August 20, 2025Khoros Communities v25.04-b16 - Release Notes
Khoros Communities v25.04-b16 is a minor update that adds a Chinese (Traditional) language pack for Taiwan (zh-TW). This is a full user interface translation. There are no functionality changes included in this release. We are planning upcoming releases during August, with important bug fixes and enhancements. Release date: 2025-07-23 (release notes delayed)Khoros Communities: Aurora 25.04 Release Notes
This release brings new tools to help you manage and protect your community. You can now move and merge content across types, mute inbox conversations, and view history for all content types. We've enhanced security checks for images and private messages, and admins can now prompt members for feedback and export their responses. Additionally, there are enhancements to GraphQL. Several bugs are also fixed.Khoros Communities: Aurora 25.03 Release Notes
The Khoros Communities: Aurora v25.03 Release introduces performance improvements, several new permissions, the ability to download your case list, moderation enhancements, post activity limit updates, improvements to the developer experience, and many bug fixes to improve the member experience.Khoros Communities: Aurora 24.12 Release Notes
This release brings enhancements for both community admins and members! Trusted members can now bypass content filters, spam rejection, and flood control limits, while admins can streamline event invites, manage SSO profiles, and maintain data integrity. Offline mode and role exclusions in Top Contributors offer more control over your community experience. Developers can enjoy a more efficient Branch Switcher with customizable branch availability. We have also fixed several bugs.Khoros Communities Aurora 24.11 Release Notes
The Communities Aurora v24.11 release contains more community language translations, the ability to edit community guidelines and privacy policies, the Content Archive feature, conversation display format defaults, improvements to the developer experience, and several bug fixes.
