Skip to content

Commit 7f0abc0

Browse files
thjaeckleclaude
andcommitted
provide Ditto 3.8.12 release notes
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
1 parent 1a46524 commit 7f0abc0

2 files changed

Lines changed: 52 additions & 0 deletions

File tree

documentation/src/main/resources/_data/sidebars/ditto_sidebar.yml

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -23,6 +23,9 @@ entries:
2323
- title: Release Notes
2424
output: web
2525
folderitems:
26+
- title: 3.8.12
27+
url: /release_notes_3812.html
28+
output: web
2629
- title: 3.8.11
2730
url: /release_notes_3811.html
2831
output: web
Lines changed: 49 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,49 @@
1+
---
2+
title: Release notes 3.8.12
3+
tags: [release_notes]
4+
published: true
5+
keywords: release notes, announcements, changelog
6+
summary: "Version 3.8.12 of Eclipse Ditto, released on 11.02.2026"
7+
permalink: release_notes_3812.html
8+
---
9+
10+
This is a bugfix release, no new features since [3.8.11](release_notes_3811.html) were added.
11+
12+
## Changelog
13+
14+
Compared to the latest release [3.8.11](release_notes_3811.html), the following changes and bugfixes were added.
15+
16+
### Bugfixes
17+
18+
This is a complete list of the
19+
[merged pull requests](https://github.com/eclipse-ditto/ditto/pulls?q=is%3Apr+milestone%3A3.8.12).
20+
21+
#### Fix background sync always detecting policy inconsistency for Things with policy imports
22+
23+
PR [#2317](https://github.com/eclipse-ditto/ditto/pull/2317) fixes an issue where background sync always detected a
24+
policy inconsistency for Things whose Policies have imports. The MongoDB projection in `sudoStreamMetadata()` was
25+
missing the referenced policies field, causing the indexed metadata to always have an empty set of referenced policies.
26+
This triggered continuous unnecessary search index updates.
27+
28+
#### Fix aggregate metrics using wrong scrapeInterval and showing 0ms duration
29+
30+
PR [#2334](https://github.com/eclipse-ditto/ditto/pull/2334) fixes two bugs in operator aggregate metrics:
31+
* `OperatorAggregateMetricsProviderActor` used the maximum configured `scrapeInterval` for all metric timers instead of
32+
each metric's own interval. Now each metric's individual `scrapeInterval` is respected, falling back to the global
33+
default.
34+
* `AggregateThingsMetricsActor` measured aggregation duration at stream materialization time instead of at stream
35+
completion time, causing the logged duration to always be ~0ms.
36+
37+
#### Fix Policy activation failure when other expired subjects exist
38+
39+
PR [#2335](https://github.com/eclipse-ditto/ditto/pull/2335) fixes a bug where `activateTokenIntegration` requests
40+
failed when the Policy contained other subjects that were already expired but still within their grace period before
41+
deletion. Now only the requested subject is checked for being expired, instead of checking the entire Policy.
42+
43+
### Helm Chart
44+
45+
#### Expose Pekko HTTP host pool max connection lifetime via Helm values
46+
47+
PR [#2336](https://github.com/eclipse-ditto/ditto/pull/2336) adds `connectivity.config.connections.httpPush.maxConnectionLifetime`
48+
to Helm values (default: `"Inf"`) and wires it to the `PEKKO_HTTP_HOSTPOOL_MAX_CONNECTION_LIFETIME` environment variable
49+
in the connectivity deployment template.

0 commit comments

Comments
 (0)