Changes 03/15/2026 (v3.9.3)
release(v3.9.3): legacy fallback worker-env fix after persistent-token key rotation
Commit message
release(v3.9.3): legacy fallback worker-env fix after persistent-token key rotation
- crypto(startup): stop exporting the legacy fallback key as a process-wide env value on compatibility-path installs
- crypto(resolve): prefer the persisted key file over legacy_default source hints once a rotation has written metadata/persistent_tokens.key
- admin(ui): eliminate post-rotation getConfig/siteConfig failures caused by workers still decrypting with the inherited legacy fallback
Fixed
- Post-rotation request consistency
- 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.php500responses until a refresh or restart. - 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.
- Fixed a case where some Apache workers could keep using the legacy fallback persistent-token key immediately after an in-app rotation, causing transient
v3.9.3
Full Changelog
SHA-256 (zip)
752cd4d14acc59e0b65127994048ce115b2dd13fb64a06ed4c64e29a9dc19760 FileRise-v3.9.3.zip