ci: wire @keryxjs/csrf into publish and test workflows#482
Merged
Conversation
The CSRF plugin introduced in #481 was never added to the publish workflow's path filter or matrix, so 0.1.1 never made it to npm. Same gap existed in the test workflow, so csrf tests were not running in CI. Bump csrf to 0.1.2 so the next push to main actually triggers a publish. Co-Authored-By: Claude Opus 4.7 (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
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
.github/workflows/publish.yaml'spathsfilter or matrix, so@keryxjs/csrf@0.1.1never published. Same gap intest.yaml, so csrf tests weren't running in CI.test-plugin-csrfjob mirroringtest-plugin-tracing) and bumps csrf to0.1.2so the next push to main actually triggers a publish.Test plan
test-plugin-csrfjob and it passes.npm view @keryxjs/csrf versionreturns0.1.2.🤖 Generated with Claude Code