[AIDockerCloud]

Summary

Upgrade TriliumNext from 0.105.0 to 0.106.1 in the Olares app triliumnext, chart version 1.0.3 -> 1.0.4.

0.106.1 is a security release for the server and Docker images — upstream explicitly asks anyone running Trilium as a server, especially internet-reachable, to update as soon as possible.

Changes (6 files, +24 −24)

File	Change
Chart.yaml	version: 1.0.3 -> 1.0.4, appVersion: 0.105.0 -> 0.106.1
OlaresManifest.yaml	metadata.version -> 1.0.4, spec.versionName -> 0.106.1, rewrite upgradeDescription
i18n/en-US + i18n/zh-CN	rewrite upgradeDescription
values.yaml	tag: 0.105.0 -> 0.106.1
templates/triliumnext.yaml	hardcoded :v0.105.0 -> :v0.106.1

Watch the tag prefix here: the template hardcodes the tag with a leading v (triliumnext/trilium:v0.106.1) while values.yaml stores it without (tag: 0.106.1). Both were updated consistently with their existing convention.

Security content

• CVE-2026-111497 — Brotli decoder out-of-bounds write. Trilium decompresses Brotli-encoded request bodies before authentication, so on earlier versions any client able to reach the server could send a malicious request. Outbound requests (link previews, image downloads, web search) were also affected through the responses they receive.
• Revoked eMudhra/emSign CAs removed from the certificate store bundled with Node.js. While trusted, a MITM with the right network position could impersonate HTTPS servers Trilium connects to (instance sync, link previews, LLM providers).
• Docker images now ship Node.js 24.22.1, taking in the October 2026 Node.js security releases (further TLS, HTTP and DNS fixes).

Also included

0.106.0 feature work: rebuilt Kanban board (column icons/colors/card limits, collapsible and archivable columns, Inbox column, card templates, board properties, automatic sorting, header filtering, multi-select).

Verification

• docker.io/triliumnext/trilium:v0.106.1 exists — confirmed against the registry tag list (0.106.x series present).
• Version fields consistent: Chart.yaml:version = metadata.version = 1.0.4; Chart.yaml:appVersion = spec.versionName = image tag = 0.106.1.
• upgradeDescription present and identical in structure across root / en-US / zh-CN (6 entries each).
• git diff --check clean; diff limited to the 6 files above.
• Single GPG-signed commit on top of upstream/main (9fe20f45), no merge commit.

Upgrade note surfaced to users

Upstream warns that if the Docker container reports unhealthy after upgrading, it should be recreated (and any healthcheck override in a compose file removed). Data format is unchanged; the existing data volume is reused as-is.

[Terminus-Gitbot]

Check passed, please wait for auto-merge.