Custom settings entries now block more template tokens
Validation of custom settings entries now blocks a wider set of literal template placeholder tokens, plus a new helper distinguishes template tokens from cc_automode region tags
Under the hoodTier: how much it should matter to you
1Useful: my rating, 1 to 5
1Signal: worth watching, 1 to 5
SettingsArea: what it touches
Internal ChangesKind: in v2.1.269,
Internal ChangesSection of the release
Unclear body was cut off; regenerating properly below
What
Validation of user-supplied settings entries (environment variables, allow/soft-deny/hard-deny rule proposals, and notes) now rejects a wider set of literal template tokens. Previously it only blocked <settings_...> and cc_automode markers; it now also blocks <user_allow_rules_to_replace>, <user_soft_deny_rules_to_replace>, <user_hard_deny_rules_to_replace>, and <user_environment_to_replace>.
A new helper function classifies a string as a "template_token" (if it contains <settings_ or matches a list of known tag names) or a "region_tag" (if it contains <cc_automode or </cc_automode>), or neither.
Why
This closes gaps that could let a settings entry contain a placeholder token that gets mistaken for real content, and gives the validation logic a clearer way to tell template placeholders apart from automode region markers.
How sure we are
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubtbody was cut off; regenerating properly below
