PRs to Categorize

• Bump minor version for release management
• Bump minor version for release management
• Remove isDefault property for named crops from li-image and li-named-crops`
• Fix back navigation for pages not linked to an issue
• Fix: small screen toolbar with css grid
• Breaking Change: Remove support for publication.updated event
• Document inbox tests
• Allow any characters in link directive urls

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

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

Webinar

• Feature Webinar Recording: TODO
• Feature Webinar Documentation: TODO
• Dev Webinar Recording: TODO
• Dev Webinar Slides: TODO
• Release Newsletter Subscription

System Requirements

Suggested

Minimal

Deployment

Before the deployment

No prior preparations (besides livingdocs-server migrate up) are required before rolling out this release.

After the deployment

No preparations are required after rolling out this release.

Rollback

Only rollback if you have a critical issue with the release in question. Usually forward patching is the better option.

If you need to rollback the release, you can do so by running the following command on the Livingdocs Server running the new release:

livingdocs-server migrate down

All document inbox entries added after the release deployment are lost when you do a rollback.

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 201-inbox-mutations.js
#   creates a copy of table document_inbox named document_inbox_v2, adapts scripts to use the new table (related to feature Document Inbox)
livingdocs-server migrate up

Migrate document_inbox table to document_inbox_v2 🔥

This release we are migrating document_inbox to a new postgres table as the data structure is changing. By migrating to the new table we can ensure a release rollback can be done more easily. However, be aware that all changes done to the inbox while running the system on release-2024-09 are lost when performing a rollback and the data before the update is restored!

Redirect URLs /p/{projectHandle}/articles/{documentId}/* to /p/{projectHandle}/document/{documentId}

All URLs of the form /p/{projectHandle}/articles/{documentId}/* will redirect to their corresponding /p/{projectHandle}/document/{documentId}/* URL. If a corresponding URL no longer exists, the URLs will redirect to the main URL /p/{projectHandle}/document/{documentId} and the associated action will no longer work.

Deprecations

NodeJS 18 ⚠️

Support for NodeJS v18 will be removed in release-2025-01. Please upgrade your docker images and local environments to node v20 or v22.

In your docker images change: FROM livingdocs/server-base:18 to FROM livingdocs/server-base:22 or FROM livingdocs/server-base:18 to FROM livingdocs/server-base:20 FROM livingdocs/editor-base:18 to FROM livingdocs/editor-base:22 or FROM livingdocs/editor-base:18 to FROM livingdocs/editor-base:20 FROM livingdocs/node:18 to FROM livingdocs/node:22 or FROM livingdocs/node:18 to FROM livingdocs/node:20

In your .nvmrc (if present) change the string from 18 to 22 or 20.

Features

Document Inbox 🎁

In a newsroom’s editorial workflow, the tasks of creating articles and placing them on a page are often divided among different roles. The document inbox is a tool that allows an article to be sent to a page’s inbox. The person responsible for managing the page can then organize the articles within the inbox using groups, and finally drag the article to a specific spot on the page.

Configuring the inbox is part of the content type configuration, in this case, for a page. By referencing a table dashboard using a handle, it’s possible to control which columns are displayed for an article entry in the inbox:

// Content Type Config
{
 handle: 'page',
 documentType: 'page',
 inbox: {
   useDashboardColumns: 'inboxDashboard', // Specifies the dashboard columns to use for the documents in the inbox
   contentTypes: ['article'], // Added in release-2024-09 
   mediaTypes: ['image'] // Pre-existing; allows media library entries in the inbox as well
 }
}

Further details can be found on the content type documentation page.

Copy & Transform flows 🎁

Document Info Panel 🎁

Document Editing Header and Toolbar 🎁

Space optimisation for side panels 🎁

The width of the wide side panels (e.g., Media Library) has been increased on large screens to provide additional space. On screens wider than 1920px, these panels will have a width of 800px. On smaller screens, the width remains unchanged at 600px.

Teaser side panels and the Document Inbox have been changed to wide side panels. They now follow the same behavior as described above: 600px on smaller screens and 800px on larger screens.

If users notice overlapping components that negatively affect their experience, please contact your CSO manager.

Dashboards: search caching behaviour 🎁

Push Message Proposals 🎁

Content Validation Errors 🎁

Table dashboards: Direct publish without safeguard 🎁

Retresco support for main entities 🎁

Retresco has introduced a new concept of main entities. These are entities identified by Retresco that are particularly relevant to a document (i.e., they have a high score). To support this new concept, we have extended our storage schema for Retresco entities to include an indicator isMain of whether an entity is a main entity and also report this data back to Retresco.

No changes are required for main entities to work, other than enabling main entities in Retresco. Currently, main entities are not marked in the Livingdocs UI. They appear as regular entities.

iMatrics test environment support 🎁

To support iMatrics test environments, we are adding a new iMatrics project configuration property to specify whether the iMatrics test environment should be used. By default, it is set to false.

integrations: {
  imatrics: {
    testEnvironment: true
  }
}

li-system-text metadata plugin 🎁

This release a new system metadata plugin becomes available: li-system-text. li-system-text is a simple text value store that behaves like li-text, but belongs to the system metadata.

It can be used in cases where a simple text value should be stored in the metadata, but the document version should not be increased when the metadata value changes. Or in other words, it will not show up as unpublished change.

Please note that it is only available as document metadata, no other contexts.

Further details can be found on the plugin documentation page.

Desknet -> Kordiam editor UI updates 🎁

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-2024-4067 patched in micromatch v4.0.8
• CVE-2024-38372 patched in undici v6.19.2
• CVE-2024-39338 patched in axios v1.7.4
• CVE-2024-41818 patched in fast-xml-parser v4.4.1

No known vulnerabilities. 🎉

Livingdocs Editor

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

• CVE-2024-4067 patched in micromatch v4.0.8
• CVE-2024-39338 patched in axios v1.7.4
• CVE-2024-42459 patched in elliptic v6.5.7
• CVE-2024-43788 patched in webpack v5.94.0

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.

Patches

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

Livingdocs Server Patches

• v257.0.2: fix(users): Support loading archived users and regular users together
• v257.0.1: fix(events): Delete unused event related to LIBREAKING035

Livingdocs Editor Patches

• v110.34.20: fix(draft-storage): Persist unsaved document to local storage on unload

• v110.34.19: chore(admin-dashboard): Filter users completely in memory

• v110.34.18: fix(ticker): Visualize ValidationErrors correctly for ticker entries

• v110.34.17: fix(assistants): disable assistants when workspace is read-only

• v110.34.16: fix(translations): Only set default locale if none is present on document create

• v110.34.15: fix(info-panel): close info panel when clicked outside

  ---

  Icon Legend

  • Breaking changes: 🔥
  • Feature: 🎁
  • Bugfix: 🪲
  • Chore: 🔧