Upcoming
release-2025-05
May 2025 Release
https://github.com/livingdocsIO/livingdocs-editor/tree/release-2025-05

Caveat 🔥

These are the release notes of the upcoming release (pull requests merged to the main branch).

  • ℹ️ this document is updated automatically by a bot (pr’s to categorize section)
  • ℹ️ this document will be roughly updated manually once a week (put PRs + description to the right section)
  • 🔥 We don’t guarantee stable APIs. They can still change until the official release
  • 🔥 Integration against the upcoming release (currently master branch) is at your own risk

PRs to Categorize

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

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

Webinar

System Requirements

Suggested

NameVersion
Node22
NPM10
Postgres16
Elasticsearch
OpenSearch		8.x
v2.3.0
Redis7
Livingdocs Server Docker Imagelivingdocs/server-base:22
Livingdocs Editor Docker Imagelivingdocs/editor-base:22
Browser SupportEdge >= 92, Firefox >= 90, Chrome >= 92, Safari >= 15.4, iOS Safari >= 15.4, Opera >= 78

Minimal

NameVersion
Node20.18
NPM10
Postgres13
Elasticsearch
OpenSearch		7.x
1
Redis6.2
Livingdocs Server Docker Imagelivingdocs/server-base:20:7
Livingdocs Editor Docker Imagelivingdocs/editor-base:20:7
Browser SupportEdge >= 92, Firefox >= 90, Chrome >= 92, Safari >= 15.4, iOS Safari >= 15.4, Opera >= 78

Breaking Changes 🔥

server Operations

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
livingdocs-server migrate up

TODO: check migration

Deprecations

Features

server/editor Exposure Boosting

Exposure Boosting 🎁

When using algorithmic teasers, the order of the documents is determined by a sort criteria. Oftentimes, this is the latest publication date. By activating the exposure boost for a document, it will appear before all non-boosted documents returned by an algorithm. This is useful, in scenarios where algorithms receive high frequency updates and important topics would get pushed down quickly. The effect will go away automatically after a certain time.

  1. Add the li-exposure-boost plugin to your content type metadata

    {
  handle: 'article',
  // ...
  metadata: [
    // ...
    {
      handle: 'exposureBoost',
      type: 'li-exposure-boost',
      config: {
        index: true
      }
    }
  ]
}
    • handle: Make sure to use the same handle for all content types where the plugin is configured
    • indexing: The config option index needs to be enabled for it to work

  2. Generally allow exposure boosting for certain teasers in their service params schema

    {
  name: 'someTeaserService',
  paramsSchema: [
    // ...
    {
      handle: 'someTeaser',
      type: 'li-teaser',
      config: {
        // ...
        algorithm: {
          // ...
          allowExposureBoost: true
        }
      }
    }
  ]
}

  3. Show the exposure boost UI on a Table Dashboard (optional)

    {
  handle: 'someDashboard',
  // ...
  columns: [
    // ...
    {
      label: 'Boost',
      minWidth: 100,
      growFactor: 0,
      priority: 1,
      metadataPropertyName: 'exposureBoost',
      editable: true
    }
  ]
}

Visit the li-exposure-boost plugin page for more information.

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:

  • TBD

No known vulnerabilities. 🎉

Livingdocs Editor

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

  • TBD

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.

Patches

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

Livingdocs Server Patches

Livingdocs Editor Patches

Icon Legend

  • Breaking changes: 🔥
  • Feature: 🎁