Skip to content

fix: retain warm OPcache reads and publish fresh cache metadata - #9

Merged
brianvarskonst merged 1 commit into
mainfrom
fix/review-20261005-cache-metadata
Oct 5, 2026
Merged

brianvarskonst merged 1 commit into
mainfrom
fix/review-20261005-cache-metadata

Conversation

@brianvarskonst

Copy link
Copy Markdown
Member

Unchanged mutable cache reads currently invalidate OPcache, and a CLI metadata publication can leave an existing FPM worker stale. Store private container/discovery metadata as atomic JSON and keep invalidation on compiled-container publication only. Restore the automatic private fallback for classic WordPress webroots and cold read-only projects while retaining rejection of unsafe explicit paths.

Validation: full package QA (77 tests, 394 assertions; strict coding standards and PHPStan), baseline reproduction, and a persistent native FPM worker with opcache.validate_timestamps=0: zero invalidations on unchanged reads, then a separate CLI publication observed by that same worker. Legacy PHP metadata is ignored and rebuilt without execution. Release: 1.1.5.

@brianvarskonst
brianvarskonst merged commit 33779b9 into main Oct 5, 2026
3 checks passed
@brianvarskonst
brianvarskonst deleted the fix/review-20261005-cache-metadata branch October 6, 2026 10:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant