A new Cloud Publishing version and Heretto Deploy API fix to portal authentication.

Cloud Publishing 25.05.25

Cloud publishing is an umbrella term for all publishing engines that come with Heretto CCMS, including PDF Generator and DITA-OT Cloud. The cloud publishing infrastructure is separate from Heretto CCMS infrastructure. New versions of cloud publishing are released separately from CCMS versions and are deployed to customers immediately after they are released.

Heretto Portal and Heretto Deploy API are separate products and are not part of cloud publishing.

• In version 25.05.25, there are no end-user updates to report. Our focus was on backend changes for future enhancements.

Heretto Deploy API 25.05.25

• Fixed. The portal now correctly returns a 401 error when an unauthenticated user requests authentication-required content. This resolves the issue where the error was not being thrown and authentication failed.

A Heretto Portal search fix and a number of improvements in the CCMS.

Heretto Portal 25.05.20

• Fixed. We resolved an issue where missing the queryString parameter in search queries caused errors for some customers using third-party search solutions. Now, these queries work without issues.

Heretto CCMS 25.05.20

• Enhanced. We addressed a behavior where users with the Author role and extra branching privileges granted by an Administrator could not branch image files and received the Insufficient privileges to perform this action error instead. Now, such users can branch all file types, including images.

• Fixed. We resolved an issue where moving files caused a Failed to retrieve requested files error. Now, files can be moved only after the CCMS completes necessary validation in the background, which prevents the error from occurring.

• Fixed. We resolved an issue where when moving a folder with locked files in the folder and its child folders, the move dialog didn't show warnings for locked files in child folders. Now, warnings are present for all locked files in the folder and its child folders.

• Fixed. We resolved an edge case where adding a topic with translate="no" to a localized map caused the topic to incorrectly receive locales (target languages). This occurred when the map was edited in the cache mode to include the new topic and then published to a target language. Now, such topics with translate="no" retain their original locale settings.

• Fixed. We resolved an issue where files with disallowed characters in their names retained those characters after upload to the CCMS, causing broken links. Now, those characters are removed or replaced with an underscore. Characters this fix applies to:

  • ' (apostrophe or single quotation mark) - gets removed

  • , (comma) - gets removed

  • ; (semi-colon) - gets removed

  • = (equal sign) - gets removed

  • ~ (tilde) - gets removed

  • + (plus sign) - gets replaced with an underscore (_)¹

• Fixed. Performance improvements when downloading locale bundles with REST API.

Fixes to Heretto Deploy API that resolve publishing and memory consumption issues.

Heretto Deploy API 25.05.19

• Fixed. We resolved an issue where portal deployments failed with the error Cannot invoke "java.util.Map.get(Object)" because "metadata" is null which was caused by files that contained no CCMS metadata. Now, deployments that contain such files publish to portal successfully.

• Fixed. We addressed a memory consumption issue caused by slow footer queries, which request content by ID instead of path. The query optimization we introduced improves stability and performance under load.

A fix to a merging issue in the CCMS.

Heretto CCMS 25.05.15

• Fixed. We resolved an issue where some merging operations between two branches failed with error message Cannot get number of files to process.

An important announcement about the next generation Heretto Deploy API (v4).

Heretto Deploy API v4

Announcement. The next generation Heretto Deploy API (v4) is being rolled out to customers. This iteration of Deploy API v4 introduces a new version of manual deployments that has been significantly redesigned and upgraded to enhance its performance and scalability.

Highlights:

• Once Deploy API v4 is enabled, during the transition period, customers will be able to use both Deploy API v3 and v4 syntax.

• Manual deployments are now processed outside of Deploy API, as a publishing job. They also separate processing a deployment from serving content. For details about the Deploy API v4 architecture, see Deploy API Overview.

• For each manual deployment, the Deployments interface now provides publishing job details. Publishing job history starts to populate once the first deployment is published.

  This change is visible to all customers who have been upgraded to v4.

  

• The structure of endpoint URLs in Deploy API v4 has changed for both active sync and manual deployments. Customers who implemented custom scripts directly against Deploy API endpoints or deliver content to third-party endpoints must update their endpoint URLs. No action is required for customers publishing only to the Heretto Portal.

  Note:

  Heretto will maintain backward URL compatibility for three months starting once the rollout of manual deployments v4 is complete. The expected end date for Deploy API v3 support is August 31, 2025. Your Customer Success Manager (CSM) will notify you of the rollout completion date, which will also be provided here.

  For detailed information about the URL changes, see Endpoint URL Changes in Deploy API v4.

A new Deploy API version with a fix for the scale attribute.

Heretto Deploy API 25.05.06

• Fixed. We resolved an issue where the scale attribute added to image elements wasn't correctly applied in Heretto Portal. For details about the scale attribute, see Important Considerations in Images.

Heretto Portal 25.05.06

• In version 25.05.06, there are no end-user updates to report.