Skip to content

chore(release): prepare 0.28.1 - #1088

Merged
joshavant merged 1 commit into
mainfrom
release/0.28.1
Nov 13, 2026
Merged

joshavant merged 1 commit into
mainfrom
release/0.28.1

Conversation

@joshavant

Copy link
Copy Markdown
Contributor

Prepare 0.28.1 using the existing tag-driven release process. Align the root package, ten platform packages, private native workspace, Rust crate, exact optional-dependency pins, and regenerated lockfiles; finalize the dated changelog for the guest temporary-name, stale-lock diagnostic, Root lock, and DrvFS fixes.

This follows the same 16-file metadata update pattern as #1077. Lockfile changes contain only the release version updates. Release dispatch, tagging, signing, and publication are outside this PR.

Validation passed on AWS Crabbox cbx_f27ecf2e836a with Node 24.22.3, pnpm 12.15.0, Rust 1.99.1, and .NET SDK 8.0.425:

  • pnpm check — 802 test files passed; 14,915 tests passed, 4,426 platform/feature skips.
  • pnpm test:security — 226 tests passed.
  • cargo test --workspace --locked
  • cargo clippy --workspace --locked -- -D warnings
  • pnpm docs:site
  • pnpm release:notes 0.28.1 — generated and inspected.
  • pnpm native:build followed by pnpm package:smoke — real Linux x64 glibc addon, npm and pnpm installed-package proof. Foreign filter fixtures do not establish foreign runtime proof.
  • git diff --check

The first validation command stopped at Clippy because the temporary Rust installation lacked that component. After installing it, all remaining checks passed on the same host; no candidate changes were needed.

Independent autoreview: GPT-6.1 Sol, medium reasoning, P0 scope; scoped-clean, no findings.

@joshavant
joshavant requested a review from a team as a code owner November 13, 2026 18:13
@clawsweeper

clawsweeper Bot commented Nov 13, 2026 •

Copy link
Copy Markdown
Contributor

🦞👀
ClawSweeper picked this up.

Pull request received. I will update this pull request when review starts.

ClawSweeper review complete

ClawSweeper finished reviewing this revision. The review result is being finalized.

View the workflow run.

@clawsweeper clawsweeper Bot added P3 Low-risk cleanup, docs, polish, ergonomics, or speculative feature. rating: 🐚 platinum hermit Good normal PR readiness with ordinary maintainer review expected. status: 👀 ready for maintainer look ClawSweeper has no concrete contributor-facing blocker left for this PR. labels Nov 13, 2026
@clawsweeper

clawsweeper Bot commented Nov 13, 2026

Copy link
Copy Markdown
Contributor

Codex review: needs maintainer review before merge.

What this changes

This PR prepares version 0.28.1 across package manifests, native-package pins, Rust metadata, lockfiles, and the changelog.

Example: Preparing the Linux x64 glibc package for release

  • Before: The root package and @openclaw/fs-safe-linux-x64-gnu both declare 0.28.0.
  • After: Both declare 0.28.1, with the root dependency pinned to that exact version.

Review scores

Measure Result What it means
Overall readiness 🐚 platinum hermit (4/6) A consistent, focused release preparation with successful package validation and no actionable findings.
Proof confidence 🌊 off-meta tidepool Not applicable: This maintainer-authored release preparation changes no runtime behavior; reported AWS Crabbox package validation and successful exact-head package smoke checks support packaging confidence without proving completed publication.
Patch quality 🐚 platinum hermit (4/6) No actionable review findings were identified.

Product

Kind: Maintenance · Worth it: Yes · Fix scope: Complete
User problem: The merged fixes need a consistently versioned package release and corresponding release notes.
Reason: The maintainer-authored preparation has established direction and follows the repository's existing release contract.

Merge readiness

✅ Ready for maintainer review

Keep this PR open for release landing: the consistent 0.28.1 preparation is absent from main, and no actionable patch defect was found.

Priority: P3
Reviewed head: 2bcc995ca94d566a919c84b9e5d482d1e7ecf0be

Before merge

None.

Findings

None.

Agent review details

How this fits together

Package manifests, native-package pins, Rust metadata, and dated release notes feed the existing protected tag workflow, which validates and publishes matching packages.

flowchart LR
 A[Package manifests] --> C[Release validation]
 B[Dated changelog] --> C
 D[Protected tag on main] --> C
 C --> E[Platform builds]
 E --> F[Package publication]
Loading

Technical review

Best possible solution:

Land the synchronized release preparation after required checks pass and publish through the existing protected tag workflow.

Do we have a high-confidence way to reproduce the issue?

There is no new bug claim to reproduce; the complete pinned diff establishes the release metadata changes directly.

Is this the best way to solve the issue?

The focused version alignment and changelog finalization preserve the established release mechanism without adding another publishing path.

AGENTS.md: found and applied where relevant.

Codex review notes: model internal, reasoning medium; reviewed against 85fef74bc2d0.

Provenance checked

  • Package, crate, native-pin, and lockfile versions keeps the original intent (27c02f7: The preceding release preparation synchronized these same metadata surfaces for 0.28.0.)
  • Pending changelog entries keeps the original intent (fix(root): retry sidecar publication handoffs #1087: Merged fixes supplied the existing user-facing notes; this PR preserves their behavior and safety qualifications while adding release organization and source links.)

Testing

Proof path: none.

Security

None.

Evidence

What I checked:

  • Pinned release diff: The introduced changes consistently update release versions and ten exact native-package pins; lockfile changes contain only matching version updates, and published changelog sections remain unchanged. (package.json:3, 2bcc995ca94d)
  • Existing release contract: The workflow requires an annotated release tag reachable from main, matching root, native workspace, crate and platform versions, exact platform pins, and dated release notes. (.github/workflows/release.yml:54, 85fef74bc2d0)
  • Prior release precedent: The merged preparation at chore(release): prepare 0.28.0 #1077 follows the same version-alignment pattern; its human follow-up records landing the exact preparation commit and tagging it through the protected workflow. (package.json:3, 27c02f710f66)
  • Exact-head validation: Retrieved checks for the reviewed head include successful bundled-package smoke checks on Linux, macOS, and Windows; several platform checks remain in progress, with no retrieved failure. (2bcc995ca94d)
  • Release still pending: Current main remains at the pinned base and declares 0.28.0; the latest published release is v0.28.0. (package.json:3, 85fef74bc2d0)
  • Related rollback inspected: The open rollback at revert(file-lock): drop crash-safe lock publication from 0.28.0 #1078 proposes separate runtime changes and mentions 0.28.1, but neither its body nor retrieved human discussion establishes a hold on this release preparation. (983c3b2de666)

Likely related people:

  • Vincent Koc: Raw commit d140ddf adds scripts/release-notes.mjs:4 relative to its recorded parents. This identifies author metadata, not feature responsibility or a PR merger. (role: source-line author; confidence: medium; commits: d140ddfdbb33; files: scripts/release-notes.mjs)

Preflight source

Source unknown. Source comparison at the observed PR snapshot only. Completion is self-reported; body, policy, tests, execution, and report bytes are not verified.

Labels

Label changes:

  • add P3: This is routine release metadata preparation with no introduced runtime change or demonstrated urgent regression.
  • add rating: 🐚 platinum hermit: Overall readiness is 🐚 platinum hermit; proof is 🌊 off-meta tidepool and patch quality is 🐚 platinum hermit.
  • add status: 👀 ready for maintainer look: ClawSweeper has no concrete contributor-facing blocker left for this PR.

Label justifications:

  • P3: This is routine release metadata preparation with no introduced runtime change or demonstrated urgent regression.
  • rating: 🐚 platinum hermit: Overall readiness is 🐚 platinum hermit; proof is 🌊 off-meta tidepool and patch quality is 🐚 platinum hermit.
  • status: 👀 ready for maintainer look: ClawSweeper has no concrete contributor-facing blocker left for this PR.

Rating scale

6/6 🦀 challenger crab · 5/6 🦞 diamond lobster · 4/6 🐚 platinum hermit · 3/6 🦐 gold shrimp · 2/6 🦪 silver shellfish · 1/6 🧂 unranked krab. Overall follows the weaker of proof and patch quality; ✨ marks media proof (a screenshot, video, or linked artifact) that directly shows the changed behavior.

Workflow

ClawSweeper edits this one comment on every review. Comment @clawsweeper re-review for a fresh review only. Repair and merge execution lanes are retired.

Reviewed November 13, 2026, 1:26 PM ET / 18:26 UTC.

@joshavant
joshavant merged commit bcf9a4a into main Nov 13, 2026
63 checks passed
@joshavant
joshavant deleted the release/0.28.1 branch November 13, 2026 18:34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

P3 Low-risk cleanup, docs, polish, ergonomics, or speculative feature. rating: 🐚 platinum hermit Good normal PR readiness with ordinary maintainer review expected. status: 👀 ready for maintainer look ClawSweeper has no concrete contributor-facing blocker left for this PR.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant