chore(deps): bump custodian pin to CAP1-aware + cwd-safe hook#304
Merged
Conversation
The custodian pin was a pre-CAP1 SHA (4a1a0aec), so venv builds and single-repo
CI ran no CAP1 even with audit.capabilities.enforce set. Bumped to 0fa072f (the
CAP1 decouple+enforce merge). Hardened the ContextGuard hook command to
${CLAUDE_PROJECT_DIR:-.} so it resolves regardless of the shell cwd.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
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.
What
4a1a0aecto0fa072f(the CAP1 decouple+enforce merge). The old pin meant the venv build and single-repo CI installed a custodian with no CAP1 detector — soaudit.capabilities.enforce: true(set in chore(custodian): enable CAP1 capability-ref enforcement #303) did nothing on this repo's own builds. With the bump, CAP1 is present (and, in a single-repo CI runner with no PlatformManifest sibling, cleanly skips — CI stays green). Thecapabilitiesplugin-audit-key shim added for the pinned-custodian doctor job stays valid and is now a no-op, since main's doctor knows the key natively.bash .claude/hooks/pre_tool_use.shtobash "${CLAUDE_PROJECT_DIR:-.}/.claude/hooks/pre_tool_use.sh"so it resolves regardless of the shell's cwd (the relative form errored non-blockingly when a tool ran from a non-root cwd).🤖 Generated with Claude Code