November 2026 Release - Operations

Upcoming

release-2026-11

November 2026 Release

https://github.com/livingdocsIO/livingdocs-editor/tree/release-2026-11

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 main 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-2026-11, 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
Release Newsletter Subscription

System Requirements

Suggested

Name	Version
Node	26
NPM	11
Postgres	18
Elasticsearch	9
OpenSearch	3
Redis	8
Valkey	9
Livingdocs Server Docker Image	livingdocs/server-base:26
Livingdocs Editor Docker Image	livingdocs/editor-base:26
Browser Support	Chrome >= 156, Edge >= 156, Firefox >= 159, Safari >= 27.0

Minimal

Name	Version
Node	22.22.0
NPM	10
Postgres	14
Elasticsearch	8
OpenSearch	2
Redis	7.4
Valkey	7
Livingdocs Server Docker Image	livingdocs/server-base:22
Livingdocs Editor Docker Image	livingdocs/editor-base:22
Browser Support	Chrome >= 142, Edge >= 142, Firefox >= 144, Safari >= 26.0

Deployment

Before the deployment

No pre-deployment steps are required before rolling out this release.

Rollout deployment

Migrate the Postgres Database

No migrations are required for this release.

After the deployment

No post-deployment steps are required after rolling out this release.

Rollback

No rollback steps are required for this release.

Breaking Changes 🔥

Minimum Node.js 22 Version Raised to 22.22.0

The supported Node.js 22 range moved from >=22.17.1 to >=22.22.0. Node.js 24 and 26 are unaffected.

undici 8 requires Node.js >=22.19.0 and posthog-node 5 requires >=22.22.0, so the previous floor advertised a minimum those dependencies never supported. Running on 22.17.1-22.21.x was already outside what those packages declare; it is now outside engines.node as well.

Node.js 22 as a whole is deprecated and will be dropped in release-2027-01, so moving to Node.js 24 or 26 is worth more than chasing a 22.x patch.

Detect

Either of:

The Node.js version running the server is 22.17.1-22.21.x. Check with node --version. An affected server emits You're using an unsupported version on boot.
A Node.js 22 patch below 22.22.0 pinned in the project - check .nvmrc, FROM lines in Dockerfiles, and CI job images. Search for 22\.(1[789]|2[01])\..

Fix

Upgrade the Node.js runtime to 22.22.0 or newer, and update every pinned version alongside it: .nvmrc, the FROM tags in Dockerfiles, and CI job images. Upgrading to Node.js 24 or 26 instead also resolves it, and avoids a second upgrade when Node.js 22 support is dropped.

npm install on an affected version reports EBADENGINE for undici and posthog-node.

Deprecations ⚠️

Features 🎁

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:

No known vulnerabilities. 🎉

Livingdocs Editor

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