release: v0.5.3 - #10
Merged
Merged
Conversation
Root cause: node/rafter-security-cli-0.1.0.tgz was committed to the repo. The test-package CI job used `ls *.tgz | head -1` which picked up the old 0.1.0 tarball (sorts before 0.5.3 alphabetically) instead of the freshly packed one. The old tarball lacks resources/ (was created before resources/ was added to the files field). Also removes node/package/ and node/package 2/ (accidentally extracted tarball contents from a previous local npm pack run). Fixes: - Remove the three committed artifacts from git - Add *.tgz, node/package/, node/package */ to .gitignore - Change CI tarball glob to rafter-security-cli-*.tgz (matches only the freshly packed tarball, not any pre-existing files) - Add test-package job to validate-release.yml so packaging is tested on every PR to prod and every push to main (not just on prod push) - Add push:main trigger to validate-release.yml Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Raftersecurity
approved these changes
Feb 21, 2026
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
2 participants
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
v0.5.3 — SARIF output, shell completions, custom patterns, agent status, Python gitleaks auto-download, and force push detection.
New Features
rafter agent scan --format sariffor GitHub/GitLab security tabs.--format text|json|sarif;--jsonremains as alias.rafter completion bash|zsh|fish~/.rafter/patterns/*.txtand*.jsonmerged with built-ins.rafterignoresuppression (Node + Python): path/glob rules to suppress findingsrafter agent status(Node + Python): config, gitleaks, hooks, OpenClaw, audit log summarybinary-manager.tsto PythonFixed
git push -f,--force-with-lease,--force-if-includes, refspec force syntax~/.rafter/bin/patterns/README written on first initVERSIONconstant innode/src/index.tswas hardcoded0.5.0; now correctnode/rafter-security-cli-0.1.0.tgzand extractednode/package/artifacts that causedtest-packageto pick up the stale tarball (missingresources/). CI glob now usesrafter-security-cli-*.tgzinstead of*.tgz | head -1.test-packagenow also runs on main pushes and PRs to prod.Tests
Test plan
validate-versions— passtest-build— passtest-package— pass (tarball containsresources/pre-commit-hook.sh, install-hook end-to-end works)🤖 Generated with Claude Code