Skip to content

security: isolate lifecycle config from consumer mappings - #286

Merged
codeforester merged 3 commits into
mainfrom
bug/264-20260901-v1-0-stop-plain-consumer-config-keys-from-changing-framework
Sep 1, 2026
Merged

codeforester merged 3 commits into
mainfrom
bug/264-20260901-v1-0-stop-plain-consumer-config-keys-from-changing-framework

Conversation

@codeforester

Copy link
Copy Markdown
Contributor

Summary

  • stop plain ConfigLoader mappings from changing environment, debug, or temp-retention lifecycle state
  • keep validated ConfigSnapshot.framework as the explicit lifecycle boundary
  • add regression coverage and migration documentation

Validation

  • pytest -q tests/test_app_run_metadata.py tests/test_batteries_included_config.py
  • ruff format/check for changed files
  • git diff --check

Fixes #264

@codeforester
codeforester merged commit 182f0c0 into main Sep 1, 2026
108 checks passed
@codeforester
codeforester deleted the bug/264-20260901-v1-0-stop-plain-consumer-config-keys-from-changing-framework branch September 1, 2026 09:06
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.

[v1.0] Stop plain consumer config keys from changing framework lifecycle

1 participant