Skip to content

[luv-cut-1.0.0-beta.1] Cut 1.0.0-beta.1 - #635

Open
NiveditJain wants to merge 1 commit into
failproofaidfrom
luv-cut-1.0.0-beta.1
Open

[luv-cut-1.0.0-beta.1] Cut 1.0.0-beta.1#635
NiveditJain wants to merge 1 commit into
failproofaidfrom
luv-cut-1.0.0-beta.1

Conversation

@NiveditJain

Copy link
Copy Markdown
Member

Release cut for 1.0.0-beta.1 — version only.

Based on failproofaid (#632) rather than main, so the diff is exactly the three version lines; the daemon work itself is reviewed on that PR.

Why a separate branch

block-version-bumps reserves package.json's version for luv-cut-* branches, and it denied the same edit on the feature branch — working as designed.

What changed

File
package.json 1.0.0-beta.01.0.0-beta.1
Cargo.toml workspace version, same bump
Cargo.lock must move with it — the release build runs cargo 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: --locked refused, --offline refreshed it, cargo build --locked then passed)

Already published

This branch was dispatched through publish.yml (dry run first, then live). Verified after the fact:

  • npm next: 1.0.0-beta.1; beta (0.0.15-beta.1) and latest (0.0.15) untouched
  • prerelease v1.0.0-beta.1 carrying four .gz binaries + SHA256SUMS
  • main's version untouched
  • the two fixes it ships confirmed on real containers — ubuntu:22.04 (glibc 2.35) and debian:12 (glibc 2.36) both run failproofaid 1.0.0-beta.1, where 1.0.0-beta.0 died with GLIBC_2.39 not found

🤖 Generated with Claude Code

https://claude.ai/code/session_01EbXKFnpRXBwsrvUJDdySky

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
@coderabbitai

coderabbitai Bot commented Jul 31, 2026

Copy link
Copy Markdown

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 617d3195-1762-4904-a105-5e1977489dc0

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • 🔍 Trigger review

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.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant