Uh oh!
There was an error while loading. Please reload this page.
[luv-cut-1.0.0-beta.1] Cut 1.0.0-beta.1 - #635
Conversation
Version only, on a `luv-cut-*` branch because `block-version-bumps` reserves package.json's version for exactly that — and it denied the same edit on the feature branch, as designed. Cargo.toml and Cargo.lock move with it: the release build runs `cargo build --locked`, which hard-errors when the lockfile records a different workspace version than Cargo.toml, so bumping one without the other would fail every cross-compile leg. Ships the two fixes 1.0.0-beta.0 surfaced on real machines — static musl Linux binaries (no glibc floor) and a system-scope service that starts at boot and survives logout. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01EbXKFnpRXBwsrvUJDdySky
Important Review skippedAuto reviews are disabled on base/target branches other than the default branch. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
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 |
Release cut for 1.0.0-beta.1 — version only.
Based on
failproofaid(#632) rather thanmain, so the diff is exactly the three version lines; the daemon work itself is reviewed on that PR.Why a separate branch
block-version-bumpsreservespackage.json'sversionforluv-cut-*branches, and it denied the same edit on the feature branch — working as designed.What changed
package.json1.0.0-beta.0→1.0.0-beta.1Cargo.tomlCargo.lockcargo build --locked, which hard-errors when the lockfile records a different workspace version, so bumping one without the other fails every cross-compile leg (verified locally:--lockedrefused,--offlinerefreshed it,cargo build --lockedthen passed)Already published
This branch was dispatched through
publish.yml(dry run first, then live). Verified after the fact:next: 1.0.0-beta.1;beta(0.0.15-beta.1) andlatest(0.0.15) untouchedv1.0.0-beta.1carrying four.gzbinaries +SHA256SUMSmain's version untouchedubuntu:22.04(glibc 2.35) anddebian:12(glibc 2.36) both runfailproofaid 1.0.0-beta.1, where 1.0.0-beta.0 died withGLIBC_2.39 not found🤖 Generated with Claude Code
https://claude.ai/code/session_01EbXKFnpRXBwsrvUJDdySky