To get an overview about new functionality, read the Release Notes. To learn about the necessary actions to update Livingdocs to release-2025-03, read on.

Attention: If you skipped one or more releases, please also check the release-notes of the skipped ones.

Webinar

• Feature Webinar Recording | Passcode: dq#S776v
• Feature Webinar Documentation
• Dev Webinar Recording | Passcode: =np2hs%&
• Dev Webinar Slides
• Release Newsletter Subscription

System Requirements

Suggested

Minimal

Breaking Changes 🔥

Migrate the Postgres Database 🔥

It’s a simple/fast migration with no expected data losses.

# run `livingdocs-server migrate up` to update to the newest database schema
# migration 206-move-revision-metadata.js
#   writes all data from table `document_metadata` to `document_revisions`
# migration 207-migration-sequence.js
#   creates two new columns `content_migration_sequence` and `metadata_migration_sequence`
#   on the `document_revisions` table
# migration 208-document-migrations.js
#   replaces the tables `document_migrations`, `document_migration_jobs`,
#   `document_migration_events`, and `document_migration_log` with new tables `document_migrations`
#   and `document_migration_jobs`. All data stored in these tables will be removed
# migration 209-asset-keys.js
#   adds support for asset keys in `media_library_entries` table
# migration 210-api-client-token-annotations.js
#   adds support for annotations in `api_client_tokens` table
livingdocs-server migrate up

Improved design version handling 🔥

All documents are now automatically bumped to the latest design version, including those passed to functions and hooks, returned by the Public API, or rendered in the Livingdocs Editor. Ensure your downstream functions, hooks, and API clients are compatible with documents delivered with the newest design version.

If a design update contains a breaking change, you must migrate all existing documents using On-Read Migrations. For more details, check out the announcement below.

To ensure a smooth transition, downstreams should verify that their stored documents are in an expected state before upgrading to this release. Specifically, ensure that only one design is in use per project and that all documents share the same design version. If these conditions are not met, applying future migrations may cause inconsistencies or errors.

To facilitate this verification, we provide a utility that performs these checks. It is available in the CLI as of release-2025-01:

Usage: livingdocs-server release-2025-03-check-document-design-versions

Checks whether all documents in a project have the same design version.

Options:
  -h, --help  Show help                                                [boolean]

If everything is in order, the following output will be displayed:

npx livingdocs-server release-2025-03-check-document-design-versions
10:16:04 INFO  cli > All documents have the same design version. You are ready to upgrade to release-2025-03.

If multiple design versions are detected, the following output will be shown instead:

npx livingdocs-server release-2025-03-check-document-design-versions
10:15:45 ERROR cli > Not all documents have the same design version. Please migrate them to the latest design version before upgrading to release-2025-03.
10:15:45 ERROR cli > projectHandle=user-nkmubrc04klh, projectId=76
10:15:45 ERROR cli >   designName=basic, designVersion=1.0.1
10:15:45 ERROR cli >   designName=basic, designVersion=1.0.0
10:15:45 ERROR cli > projectHandle=user-bbab7sud5ap8, projectId=77
10:15:45 ERROR cli >   designName=basic, designVersion=1.0.0
10:15:45 ERROR cli >   designName=basic, designVersion=1.0.1
10:15:45 ERROR cli > projectHandle=user-vn89gm58rxhu, projectId=78
10:15:45 ERROR cli >   designName=basic, designVersion=1.0.1
10:15:45 ERROR cli >   designName=basic, designVersion=1.0.0

In that case, documents should be migrated using CLI data-migration-run before upgrading to release-2025-03.

Server configs projectConfigs.showMigrationUi and projectConfigs.autoDesignMigrations 🔥

Server config properties projectConfigs.showMigrationUi and projectConfigs.autoDesignMigrations are no longer supported due to the improved design version handling. As part of this change, the design migration page has been removed from the Editor. Please remove these properties from your server config.

CLI data-migration-run no longer supports options --design-version-to and --filter-by-design-version 🔥

The CLI data-migration-run no longer supports options --design-version-to and --filter-by-design-version due to the improved design version handling.

Migration APIs replaced with migrationApi.run() 🔥

The following Server APIs have been removed:

• migrationApi.listMigrations
• migrationApi.resumeAllMigrations
• migrationApi.getMigration
• migrationApi.createMigration
• migrationApi.updateMigration
• migrationApi.prepareMigration
• migrationApi.acceptMigration
• migrationApi.cancelMigration
• migrationApi.getMigrationReport
• migrationApi.getMigrationLogs
• migrationApi.runMigration

Please use server API migrationsApi.run instead.

Removal of deprecated document URLs /p/{projectHandle}/document/{documentId} 🔥

All deprecated editor routes are removed and will redirect to the new base editor URL: /p/{projectHandle}/document/{documentId}. They include:

• /p/{projectHandle}/articles/{documentId}/edit/add
• /p/{projectHandle}/articles/{documentId}/edit/canvas/component/{componentId}
• /p/{projectHandle}/articles/{documentId}/edit/component/{componentId}
• /p/{projectHandle}/articles/{documentId}/history
• /p/{projectHandle}/articles/{documentId}/history/compare/:revisionFromId/with/:revisionToId
• /p/{projectHandle}/articles/{documentId}/history/{revisionId}
• /p/{projectHandle}/articles/{documentId}/edit/notifications/unsubscribe
• /p/{projectHandle}/articles/{documentId}/publish
• /p/{projectHandle}/articles/{documentId}/edit/canvas/tasks

Removal of Angular services ldEditApi and serverApi

Angular services ldEditApi and serverApi have been removed. Please use Angular service storage instead.

Removal of video and file support from document inbox

Support for media types mediaVideo and mediaFile has been removed from the document inbox. We don’t expect this to break any customer setup and this change does not delete any data. In case you see a removal warning after the update, please reach out to us and we find will a solution.

Deprecations

Server APIs projectApi.getStats and designStatsApi.listDesigns ⚠️

Server APIs projectApi.getStats and designStatsApi.listDesigns are deprecated and will be removed in release-2025-09.

li-images and li-videos ⚠️

The internal li-images and li-videos feature APIs are deprecated and will be removed in release-2025-07. Please use li-media-library.

Features

API versioning 🎁

We’re introducing a new API Versioning Strategy that allows us to iterate on the API without breaking existing integrations.

With the introduction of a new versioning strategy, the v1 and beta versions are now available as 2025-03 version. If you use any of those versions, you can safely change your integration to the 2025-03 version, which now contains both functionalities without any other changes.

Improved design version handling 🎁

All documents are now automatically bumped to the latest design version, including those passed to functions and hooks, returned by the Public API, or rendered in the Livingdocs Editor. To ensure compatibility with the newest design version, you need to define the necessary On-Read Migrations.

On-Read Migrations are applied whenever a document is read from the database. This means they take effect immediately, allowing all hooks, functions and clients consuming the data to work with the updated document structure.

1. Define your migrations in the Project Config for each content type, referencing a migrate function.

   {
     handle: 'article',
     ...
     migrations: [
       {
         sequence: 1,
         migrateFunctionHandle: 'removeComponent',
         context: {componentName: 'subtitle'}
       },
       {
         sequence: 2,
         migrateFunctionHandle: 'renameMetadataProperty',
         context: {from: 'description', to: 'lead'}
       }
     ]
   }
   

   • sequence: Specifies the execution order of migrations. Values must be unique and increasing.
   • migrateFunctionHandle: References a registered migrate function (see below).
   • context: Optional data passed to the migrate function, enabling reuse of migrate functions.
   Migrations should not be removed once added. In a future release, a mechanism will allow running migrations in the background to support safe removal. Until then, only append new migrations.

2. Register the migrate function in the function registry. Migrate functions are registered using liServer.registerMigrateFunctions. Alternatively, individual migration functions can be registered using liServer.registerMigrateFunction.

   Only synchronous migrate functions are supported.

   liServer.registerMigrateFunctions([
     {
       handle: 'removeComponent',
       migrateContent({content, context}) {
         return {content}
       }
     },
     {
       handle: 'renameMetadataProperty',
       migrateMetadata({metadata, metadataSource, translations, context}) {
         return {metadata, metadataSource, translations}
       }
     }
   ])
   

   • handle: Matches the migrateFunctionHandle in the project configuration.
   • migrateContent: Modifies a document’s content.
   • migrateMetadata: Modifies metadata, metadataSource, and translations (if applicable).

Data migration improvements 🎁

Data Migrations, usually executed using the data-migration-run CLI, have received several improvements:

• Data Migrations are executed in a single step, with the result written back to the database immediately, eliminating the separate prepare and accept phases. This significantly reduces version conflicts caused by users actively editing documents during migrations. If a data migration still fails due to version conflicts, it is automatically retried up to three times.
• The migrateAsync functions now receive two additional parameters: metadataSource and translations. These parameters can also be modified and returned.
• After data migrations are executed, statistics and references are re-extracted.
• The CLI command data-migration-run now includes two new options: --filter-by-id-from and --filter-by-id-to, allowing migrations to be applied to a specific range of documents.

Media Center: Image variant Storage / Delivery 🎁

To enable this functionality, an opt-in configuration has been added:

mediaLibrary: {
  use2025Behavior: true
}

Resized and cropped image variants are stored in the image storage under the image-variants-cache/ prefix. To manage storage efficiently, we recommend setting up a retention policy for these cached variants in your blob storage provider.

If the main storage does not support image variants, you can use the variantsStorage configuration to store resized images in a separate bucket. This is optional—by default, the system saves variants in the same storage as the original images.

mediaLibrary: {
  use2025Behavior: true,
  images: {
    storage: {
      strategy: 's3',
      config: {
        bucket: 'images',
        // ...
      }
    },
    variantsStorage: {
      strategy: 's3',
      config: {
        bucket: 'image-variants',
        // ...
      }
    }
  }
}

Additionally, we’ve introduced a new public API endpoint:

/api/2025-03/mediaLibrary/serve-image/:key

This endpoint delivers the image with its original dimensions, as long as it has not been revoked or marked as invalid.

Looking ahead, we plan to introduce more advanced image processing capabilities beyond cropping and resizing in future releases.

Media Center: Archive/Revoke/Delete 🎁

We have made some opt-in changes to the media library to provide more clarity around the available actions for media library entries. The new behaviour will be enabled when the mediaLibrary.use2025Behavior server config property is set to true.

When you enable the new behavior you will notice that the Archive action has been removed from the UI at the bottom of the media library entry detail page. To recap, this action removed the entry from Elasticsearch, and therefore all dashboards, but the image still existed in Postgres and remained in documents it had already been added to.

Revoke remains largely the same, with the same hooks etc. The main change is that we no longer delete the image from the storage bucket so that we retain the image for legal cases. The new image delivery route will prevent the image from being served, but the imgix cache will still need clearing using the hook.

Delete has been introduced as a replacement for the Archive action. Delete completely removes the data from databases and storage. Deleting an entry is only possible when it is not referenced, is not in a document inbox, is not stored in the archive, and has never been published in a document.

Finally, a new Store in Archive action has been added (along with Remove from Archive). This sets a state on the media library entry which prevents its deletion.

Please read the information about Media Center: Image variant Storage / Delivery before enabling use2025Behavior, as the two features are linked together with the same server config property.

Smart quotes 🎁

Typography plays a crucial role in journalism, ensuring that text maintains a professional and polished appearance. However, most standard keyboards do not provide an easy way to input typographically correct quotation marks.

To address this challenge, Livingdocs introduces the Smart Quotes feature, which automatically replaces quotation marks as you type with the appropriate ones defined in your configuration. This enhancement helps editors maintain high-quality typography without manual effort. With the provided switch in the editor UI, users are allowed to disable the feature when necessary for special cases.

How to Use Smart Quotes

To enable the Smart Quotes toggle, the smartQuotes property must be added to the textFormatting configuration. This can be done in editor_settings.js. You can also overwrite this config for each content type.

Additionally, either the quotes & singleQuotes properties or the locales property must be set in textFormatting, as these will be used as replacement quotes.

// Either in editor_settings.js or content-types/*
textFormatting: {
  smartQuotes: {enabled: true}, // Alternatively: `smartQuotes: true``
  quotes: ['«', '»'],
  singleQuotes: ['‹', '›'],
  // Either quotes and singleQuotes OR locales need to be set
  locales: {
    en: {
      quotes: ['“', '”'],
      singleQuotes: ['‘', '’']
    },
    de: {
      quotes: ['«', '»'],
      singleQuotes: ['‹', '›']
    }
  }
}
// ...

Once configured, the Smart Quotes toggle will be available in the editor on the bottom left corner. Each time a document is opened, the toggle will be turned on by default. Users can turn off the toggle when needed, allowing flexibility for special cases where standard quotation marks are required.

Page Management: Teaser Container with List & Algorithm 🎁

In real-world page management scenarios, teasers often come in groups. It can be tedious to define and manage the details for every single teaser if you just want them to be the same.

With teaser containers, we let editors change the Algorithm and Curated List on a group level and all the teasers in the group will be updated with the same settings. Setting a Direct Reference on individual teasers is still possible.

There are two prerequisites for this feature:

• The teaser group component uses a doc-container with the config isTeaserContainer: true
• All the teasers in the group are using an identical li-teaser config in their include service params

For further information, or if you are using the Command API to update teasers, please read up all the details on the li-teaser documentation page.

Page Management: Teaser Side Table 🎁

In a typical page management use case, an article might “tickle down” the page throughout the day. Editors can place a particular article on a teaser by setting it as a direct reference (Level 1). Whenever an article was set as the direct reference for a teaser, it might replace the previous article. So if the previous article also needs to be moved somewhere else, Editors have a hard time keeping track of them.

So instead of just letting the previous article fall on the floor, we temporarily store it on the Teaser Side Table. From there, Editors can pick it up again and drag it to the desired location.

For further information, please read up all the details on the li-teaser documentation page.

Document Inbox: Image Support 🎁

Images have been supported in the Inbox for a long time, but they did not yet have the same sorting and grouping features we added for Documents in 2024.

We are happy to announce that this is now possible for images too. And like documents, images can be in the same inbox multiple times. Images can even be added to an inbox directly from within the inbox. All your images sitting already in an inbox will automatically appear at the top of the inbox, just next to the documents. From there, you can start organizing them in the same groups alongside documents.

Technically, the inbox also supported videos and files. To our knowledge, this has never been set up by any of our customers. We decided to remove the support for Videos and Files in Inboxes altogether. This decision allowed us to optimize the user experience for the two things our customer care about the most: Documents and Images.

For further information, please read up all the details on the Content Type documentation page.

Vulnerability Patches

We are constantly patching module vulnerabilities for the Livingdocs Server and Livingdocs Editor as module fixes are available. Below is a list of all patched vulnerabilities included in the release.

Livingdocs Server

This release we have patched the following vulnerabilities in the Livingdocs Server:

• CVE-2025-22150 patched in undici v6.21.1
• [CVE-2025-27152] patched in axios v1.8.2

No known vulnerabilities. 🎉

Livingdocs Editor

This release we have patched the following vulnerabilities in the Livingdocs Editor:

• CVE-2025-22150 patched in undici v6.21.1
• [CVE-2025-27152] patched in axios v1.8.2

We are aware of the following vulnerabilities in the Livingdocs Editor:

• CVE-2023-44270 vulnerability in postcss, it affects linters using PostCSS to parse external Cascading Style Sheets (CSS). It is not exploitable in the editor as we don’t load untrusted external CSS at build time.
• CVE-2023-26116, CVE-2023-26118, CVE-2023-26117, CVE-2022-25869, CVE-2022-25844 are all AngularJS vulnerabilities that don’t have a patch available. We are working on removing all AngularJS from our code and vulnerabilities will go away when we complete the transition to Vue.js.
• CVE-2024-6783 vulnerability in vue-template-compiler it allows malicious users to perform XSS via prototype pollution. Editor build is always done in a trusted environment and the vulnerability is not exploitable.
• CVE-2024-9506 vulnerability in vue, an ReDoS vulnerability exploitable through inefficient regex evaluation in parseHTML function. The issue can cause excessive CPU usage but is not exploitable in the editor as we don’t load untrusted HTML at runtime.

Patches

Here is a list of all patches after the release has been announced.

Livingdocs Server Patches

• v271.0.19: fix: Apply crops in top left corner of an image

• v271.0.18: fix(li-image): Re-add the config.readOnly attribute on li-media

• v271.0.17: fix(image-variants): add cloudinary storage fetch implementation

• v271.0.16: fix(menu-tool): Log deprecation warnings in menu API

• v271.0.15: fix(history): Show more than 100 revisions

• v271.0.14: fix(logger): Do not try to serialize streams in pino serializer for axios

• v271.0.13: fix(deps): update dependency axios from 1.7.9 to 1.8.2 [security]

• v271.0.12: fix(design-version-update): Account for migratedDocumentVersionDelta when component condition is triggered

• v271.0.11: fix(image-variants): rename url path to serve-image instead of serve-images

• v271.0.10: fix: Throw breaking change messages

• v271.0.9: chore: Enable auto pipelining for queue redis connections

• v271.0.8: fix(li-task-v2): Only show task mode in notifications if mode is configured

• v271.0.7: fix(li-task-v2): Prevent notification composition failure when no modes are defined

• v271.0.6: fix(design-version-update): Account for migratedDocumentVersionDelta when setting model version after an update

• v271.0.5: fix(image-variants): azure blob storage now handles 404 correctly

• v271.0.4: fix(media-library): Prevent serving invalid images

• v271.0.3: fix(webhooks): Add webhook timeout config property

• v271.0.2: fix(api-version): Keep supporting beta routes

Livingdocs Editor Patches

• v115.22.32: fix: Show content type label instead of content type handle in li-document-resource

• v115.22.31: fix(media-library): Check entry exists before displaying archive icon

• v115.22.30: fix(peiq): make system name ‘peiq’ lowercase

• v115.22.29: fix(dashboards): Add li-kordiam-integration to supported columns

• v115.22.28: fix(toolbar): Make document dashboard active state reactive

• v115.22.27: fix(li-button–bar): Long labels

• v115.22.26: fix(media-library): Show image for current locale in lightbox

• v115.22.25: fix(history): Load old designs of revisions in the history view

• v115.22.24: fix(assistants): save field extractor changes after assistant finished

• v115.22.23: fix(inbox): implicit breaking change - remove support for video and file

• v115.22.22: fix(image-variants): rename url path to serve-image instead of serve-images

• v115.22.21: fix(creation flow metadata form): suppress workspace injection warning

• v115.22.20: fix(li-distribution-dates): avoid saving without valid date

• v115.22.19: fix(task-screen): Open documents with task panel open

• v115.22.18: fix(peiq): do metadata extraction when replacing an image

• v115.22.17: fix(media library): detail details

• v115.22.16: fix: scroll fixes in editor view

• v115.22.15: fix: fix var names in translations

• v115.22.14: fix: Fix documentation links

• v115.22.13: fix(trackjs): sanitize Bearer, Basic, and Authorization strings in payload

• v115.22.12: fix: use Print instead of Druck for german print version labels

• v115.22.11: fix(distribution dates): Polish

• v115.22.10: fix(image-variants): strip path prefix was not passed to the variants image service

• v115.22.9: fix(side table): Item title

• v115.22.8: fix(media-library): Only show “Store in Archive” when use2025Behavior

• v115.22.7: fix(media-library): Rename preserveOriginalAssets to use2025Behavior (Part II)

• v115.22.6: chore(comments): Remove tributejs dependency

• v115.22.5: fix(format-popover): Do not let format popover slip behind preview panel

• v115.22.4: fix(media library): Side panel z-visibility

• v115.22.3: fix: Open document inbox when in visibility mode

Icon Legend

• Breaking changes: 🔥
• Feature: 🎁