chore(release): 0.4.2 - #52
Merged
Merged
Conversation
Ships the security audit: #46, #47, #50 and #51. All four are on main and none are reaching anyone — the endpoint serves what PINS says, and PINS still points at v0.4.1, which predates every one of them. install.sh on main f38612c071bcd6d4... served (v0.4.1) 639b4167471082c6... What this releases: #46 install-hooks.{sh,ps1} fetched six executables from a mutable branch with no verification, chmod +x'd them, and pointed core.hooksPath at them — on every fresh onboard, since resq is installed after hooks run. Now pinned and digest-checked, failing closed. #47 TLS pinning across scripts/lib; nix.sh piped 4xx bodies into sh; bun.sh fetched schemelessly; docker.sh used apt-key, which grants the Docker key authority over every repository on the system. #50 Nix installer pinned to a versioned URL and verified; Docker installed from its GPG-signed apt repo rather than get.docker.com; installer failures no longer report success; Debian and Ubuntu suites resolved correctly. #51 Bun's installer pinned to a tagged copy and verified. Merging this is the release. Merging the pin-bump PR that follows is what changes the served bytes. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Deploying with
|
| Status | Name | Latest Commit | Updated (UTC) |
|---|---|---|---|
| ✅ Deployment successful! View logs |
get-resq-software | e1694f2 | Aug 11 2026, 10:55 AM |
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (3)
📝 WalkthroughWalkthroughThe project version and both installer script versions were incremented from ChangesRelease version alignment
Estimated code review effort: 1 (Trivial) | ~2 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 |
resq-sw
approved these changes
Aug 11, 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
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.
Ships the security audit — #46, #47, #50 and #51. All four are on
mainand reaching nobody: the endpoint serves whatPINSsays, andPINSstill points atv0.4.1, which predates every one of them.What this actually releases
install-hooks.{sh,ps1}no longer fetch six executables from a mutable branch unverified,chmod +xthem, and pointcore.hooksPathat them — which happened on every fresh onboard, sinceresqis installed after hooks runscripts/lib;nix.shno longer pipes 4xx bodies intosh;bun.shno longer fetches schemelessly;apt-keygone, so the Docker key no longer has authority over every repo on the systemget.docker.com; installer failures no longer report success; Debian and Ubuntu suites resolved correctlyDiff
Three lines:
VERSION, and the twoSCRIPT_VERSIONvaluesbin/stamp.shpropagates. Every digest constant was already correct onmain, so nothing else moves.Sequence
Merging this is the release —
release.ymlfires onpaths: VERSION, tagsv0.4.2, publishes the Release andSHA256SUMS, and opens the pin-bump PR. Merging that second PR is what changes the served bytes.Verified locally:
stamp --checkin sync at 0.4.2, shellcheck clean, 48/48 worker tests.🤖 Generated with Claude Code
Summary by CodeRabbit