Update Homebrew formula to CodeTruss CLI v0.2.30 - #3
Conversation
The formula was serving 0.2.24 while the product shipped 0.2.30. - Point url at the v0.2.30 release archive and pin its SHA-256 9c97f573aa7e7a052fe8d4c578efda6a8d43f2bcfec9a74ab7d2fdf6b53eccdc, taken from the published .sha256 sidecar and confirmed against the downloaded bytes. - Update the CI version assertion, which still hardcoded 0.2.24 and would have failed the moment the url moved. - Move desc and the README lede to the first-pass verification gate language. The install and test blocks were audited against the real 0.2.30 tarball and needed no change: the archive still unpacks to exactly the eight installed paths, dist/cli.cjs still carries its shebang and executable bit so the symlink works, `codetruss --version` prints "codetruss 0.2.30" so the version-derived assertion holds, and `codetruss init --allow "src/**"` still writes a .codetruss.yml containing "- src/**". Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
📝 WalkthroughWalkthroughCodeTruss release references now target v0.2.30. The Homebrew formula uses the new archive checksum, the workflow checks the new version, and the README describes the current verification flow. ChangesCodeTruss release update
Estimated code review effort: 1 (Trivial) | ~3 minutes Possibly related PRs
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@Formula/codetruss.rb`:
- Around line 4-5: Ensure the v0.2.30 release and its codetruss-cli-0.2.30.tgz
asset are published and accessible at the URL configured by the formula’s url
and sha256 declarations, or update those declarations to reference an existing
published release and matching checksum before merging.
🪄 Autofix
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: defaults
Review profile: CHILL
Plan: Pro Plus
Run ID: f57cd735-4dba-4cea-9689-cd625867951c
📒 Files selected for processing (3)
.github/workflows/test.ymlFormula/codetruss.rbREADME.md
|
CI result is the expected one, and it is the only problem:
Sequence: merge codetruss-cli#16, |
Important
Merge this after the
v0.2.30CLI release is cut. The formula points atthe v0.2.30 GitHub release asset, which does not exist yet. CI will fail with a
404 until DeliriumPulse/codetruss-cli#16
merges and the
v0.2.30tag is pushed. Re-run CI then and it should go green.The formula was serving 0.2.24 while the product shipped 0.2.30.
Changes
urlmoved to the v0.2.30 release archive,sha256pinned to9c97f573aa7e7a052fe8d4c578efda6a8d43f2bcfec9a74ab7d2fdf6b53eccdc.codetruss 0.2.24and would have failed the moment the url moved. Now0.2.30.descand the README lede moved to the first-pass verification gate language.Per the README's release policy, url, SHA-256, and the formula test were updated
together, and the target is a published immutable release.
Verification
codetruss-cli-0.2.30.tgzfrom codetruss.com, hashed it locally, and matched both the published.sha256sidecar and the pinned value. The release asset is the same deterministic artifact as the website archive, which is how 0.2.24 lined up too.ruby -cclean.brew style Formula/codetruss.rbreports no offenses.CHANGELOG.md,LICENSE,README.md,SBOM.cdx.json,SECURITY.md,THIRD_PARTY_NOTICES.md,dist,package.json), so nothing is missing or extra.dist/cli.cjsstill carries#!/usr/bin/env nodeand the executable bit.--versionprintscodetruss 0.2.30, matching the URL-derived#{version}, andcodetruss init --allow "src/**"still writes a.codetruss.ymlcontaining- src/**.brew install --build-from-sourcesemantics are unchanged: this is still aprebuilt bundled executable with a
nodedependency and no compile step, so theflag only skips bottle lookup as before.
🤖 Generated with Claude Code
Summary by CodeRabbit
New Features
Chores