chore(claude): track claude-security plugin as enabled - #326
Merged
Conversation
The deployed ~/.claude/settings.json has had claude-security@claude-plugins-official enabled since the plugin was turned on at runtime, but the chezmoi source was never updated. A `chezmoi apply` would therefore have silently disabled the plugin. Record the entry in source so the deployed state and the managed source agree. After this commit the source file is byte-identical to the deployed one (blob 0dd8bd7). Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
|
| Filename | Overview |
|---|---|
| private_dot_claude/settings.json | Adds one valid official-marketplace plugin entry without violating repository plugin or update-policy constraints. |
Reviews (1): Last reviewed commit: "chore(claude): track claude-security plu..." | Re-trigger Greptile
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
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.
Summary
The deployed
~/.claude/settings.jsonhas carriedclaude-security@claude-plugins-official: truesince the plugin was enabled at runtime, but the chezmoi source was never updated to match. Runningchezmoi applywould therefore have silently disabled the plugin.This records the entry in source so the managed source and the deployed file agree.
Why now
The drift surfaced while reviewing an unrelated change:
chezmoi diffon~/.claude/settings.jsonshowed a third hunk removing this line, which had nothing to do with the change under review. Kept separate from that work deliberately.Verification
python3 -c "json.load(...)"— file parses;enabledPluginsgains exactly one entrypython3 tests/codex/verify_claude_update_policy.py—OK: Claude/Codex update policy source settings match ADR 00260dd8bd7, byte-identical to the currently deployed~/.claude/settings.json, sochezmoi difffor this file is now emptyRisk
None to behaviour: the deployed state is unchanged. This only stops a future
chezmoi applyfrom reverting it.🤖 Generated with Claude Code