ci(claude-code): run the plugin test suite in CI#42
Merged
Conversation
The plugin's pytest suite was never executed by CI: validate.yml only checks integration.yaml schemas under integrations/ and does not touch claude-code/, so every regression test added only ran when someone ran it by hand. Adds a workflow (triggered on claude-code/** changes) with two jobs: - stdlib: pytest with NO crypto packages, asserting the SessionStart hook and drift check work on the standard library alone (signing tests skip via importorskip; an accidental dependency on them fails the build). - signing: pip install -r requirements.txt then the full suite across Python 3.11 / 3.12 / 3.13, exercising the sign / publish / verify path. Verified locally: stdlib env -> 13 passed, 2 skipped; crypto env -> 15 passed. Co-Authored-By: Claude Opus 4.8 (1M context) <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.
Follow-up to #41. The plugin's pytest suite was never run by CI —
validate.ymlonly validatesintegration.yamlschemas underintegrations/and doesn't touchclaude-code/. So all the regression tests we've added (verify fix, hook hardening, signing/verification) only ran locally.Adds
.github/workflows/claude-code-tests.yml, triggered onclaude-code/**changes, with two jobs:importorskip; an accidental hard dependency on crypto would fail this job.pip install -r requirements.txtthen the full suite across Python 3.11 / 3.12 / 3.13, exercising the sign → publish → verify path.Verified locally: stdlib env → 13 passed, 2 skipped; crypto env → 15 passed.
🤖 Generated with Claude Code