Repository navigation
Remove persisted process-secret verifiers from environment caches - #29
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Compiled environment templates refresh interpolated process values on every warm request without persisting value-derived fingerprints. Production Doctor checks the signing key, trusted proxy handling includes mapped IPv6, and a read-only EnvironmentInspection API exposes the same file/cache precedence safely.
Validation: complete PHP QA, 1381 tests/10091 assertions with real WordPress and database; cold/warm/rotated-template benchmark, documentation contracts and leak/rotation regressions passed.