Repository navigation
chore(release): prepare 0.28.1 - #1088
Conversation
|
🦞👀 Pull request received. I will update this pull request when review starts. ClawSweeper review completeClawSweeper finished reviewing this revision. The review result is being finalized. |
|
Codex review: needs maintainer review before merge. What this changesThis 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
Review scores
ProductKind: Maintenance · Worth it: Yes · Fix scope: Complete 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 Before mergeNone. FindingsNone. Agent review detailsHow this fits togetherPackage 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]
Technical reviewBest 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
TestingProof path: none. SecurityNone. EvidenceWhat I checked:
Likely related people:
Preflight sourceSource unknown. Source comparison at the observed PR snapshot only. Completion is self-reported; body, policy, tests, execution, and report bytes are not verified. LabelsLabel changes:
Label justifications:
Rating scale6/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. WorkflowClawSweeper edits this one comment on every review. Comment Reviewed November 13, 2026, 1:26 PM ET / 18:26 UTC. |
Prepare
0.28.1using 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_f27ecf2e836awith 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 --lockedcargo clippy --workspace --locked -- -D warningspnpm docs:sitepnpm release:notes 0.28.1— generated and inspected.pnpm native:buildfollowed bypnpm package:smoke— real Linux x64 glibc addon, npm and pnpm installed-package proof. Foreign filter fixtures do not establish foreign runtime proof.git diff --checkThe 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.