Skip to content

Commit a83f88b

Browse files
chore: sync CHANGELOG.md + VERSION (v3.9.3) from FileRise
1 parent d04d84f commit a83f88b

2 files changed

Lines changed: 23 additions & 1 deletion

File tree

CHANGELOG.md

Lines changed: 22 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,27 @@
11
# Changelog
22

3+
## Changes 03/15/2026 (v3.9.3)
4+
5+
`release(v3.9.3): legacy fallback worker-env fix after persistent-token key rotation`
6+
7+
**Commit message**
8+
9+
```text
10+
release(v3.9.3): legacy fallback worker-env fix after persistent-token key rotation
11+
12+
- crypto(startup): stop exporting the legacy fallback key as a process-wide env value on compatibility-path installs
13+
- crypto(resolve): prefer the persisted key file over legacy_default source hints once a rotation has written metadata/persistent_tokens.key
14+
- admin(ui): eliminate post-rotation getConfig/siteConfig failures caused by workers still decrypting with the inherited legacy fallback
15+
```
16+
17+
**Fixed**
18+
19+
- **Post-rotation request consistency**
20+
- Fixed a case where some Apache workers could keep using the legacy fallback persistent-token key immediately after an in-app rotation, causing transient `getConfig.php` / `siteConfig.php` `500` responses until a refresh or restart.
21+
- Compatibility-path installs no longer export the legacy fallback key as a worker-wide env value, and the key resolver now prefers the persisted key file once rotation has written `metadata/persistent_tokens.key`.
22+
23+
---
24+
325
## Changes 03/15/2026 (v3.9.2)
426

527
`release(v3.9.2): admin config decrypt retry after persistent-token key transitions`

VERSION

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1 +1 @@
1-
v3.9.2
1+
v3.9.3

0 commit comments

Comments
 (0)