[steipete]

Prepare imsg 0.21.0, a minor release for mentions in rich and multipart sends, attached-sticker placement, and explicit Messages Name & Photo setters. It also includes the accumulated typing, subject, delivery-verification, deletion, dependency, and CI fixes.

Synchronize all generated version metadata, preserve every existing changelog bullet and contributor credit, and leave the post-release Unreleased section in place. The release notes explicitly state that #365, #366, and #377 were fixture-tested only, without live sends or account identity changes.

Validation: all four version sources agree; all 316 existing changelog bullets are preserved; docs tests pass (2/2); independent Codex review is scoped-clean through P2. Exact-head CI and the full signing/notarization release dry run are required before publication.

[clawsweeper]

🦞👀
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.

[chatgpt-codex-connector]

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review	Status	Commit	Review trigger
📝 Code Review	✅ Completed 2026-11-05T19:18:58.814098Z	8fa910a	PR opened

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

[clawsweeper]

Codex review: needs maintainer review before merge.

What this changes

Prepares imsg 0.21.0 by adding release highlights and synchronizing CLI, helper, and bundle version metadata.

Example: Read the CLI release version after building this revision.

• Before: The version is 0.20.0.
• After: The version is 0.21.0.

Review scores

Measure	Result	What it means
Overall readiness	🦐 gold shrimp (3/6)	The small patch is consistent and supported by passing platform CI; evidence remains static and CI-based rather than a demonstrated shipped version-output run.
Proof confidence	🦐 gold shrimp (3/6)	This maintainer-authored PR only prepares release notes and version metadata, so the ordinary contributor proof gate does not apply; passing CI supports validation but does not establish live behavior for the previously merged features.
Patch quality	🐚 platinum hermit (4/6)	No actionable review findings were identified.

Product

Kind: Maintenance · Worth it: Yes · Fix scope: Complete
User problem: The accumulated changes on main need a dated release entry and consistent 0.21.0 version identification.
Reason: The maintainer-authored preparation follows the established minor-release pattern and accurately preserves the existing release contents and credits.

Merge readiness

✅ Ready for maintainer review

Keep open: this maintainer-authored release preparation is still needed, and the focused diff has no actionable defects.

Priority: P3
Reviewed head: 8fa910a7af645142f3331842ead71e8bb0548332

Before merge

None.

Findings

None.

Agent review details

How this fits together

The canonical version.env feeds generated CLI, injected-helper, and macOS bundle metadata; the release workflow validates those values alongside the dated changelog section.

flowchart TD
  A[Canonical version.env] --> B[Version generator]
  B --> C[CLI version]
  B --> D[Helper version]
  B --> E[Bundle metadata]
  F[Dated changelog] --> G[Release validation]
  A --> G

Loading

Technical review

Best possible solution:

Land the consistent release metadata, then follow the documented verification and publication procedure.

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

There is no reported runtime bug to reproduce; the pinned diff directly establishes the release metadata change.

Is this the best way to solve the issue?

The change follows the existing release pattern and uses the canonical version generator's existing outputs without adding another owner or behavior path.

AGENTS.md: found and applied where relevant.

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

Provenance checked

• CLI, helper, bundle, and canonical version metadata keeps the original intent (5af52a0: The previous release preparation synchronized these same version surfaces for 0.20.0.)
• Changelog release boundary keeps the original intent (1aca78d: The existing Unreleased section collects changes after a verified release; this PR retains it and places accumulated entries under the next dated release.)

Testing

Proof path: none.

Security

None.

Evidence

What I checked:

• Focused release preparation: The introduced diff adds the dated 0.21.0 section and highlights, retains Unreleased and every existing changelog bullet, and changes all version values consistently from 0.20.0 to 0.21.0. (CHANGELOG.md:5, 8fa910a7af64)
• Repository policy applied: Read the complete root policy; no nested AGENTS.md, maintainer-notes directory, or pr-simplify skill exists in this checkout. (AGENTS.md:1, 8fa910a7af64)
• Release ordering: The documented procedure merges release preparation before running the signing/notarization dry run on green main; that dry run must succeed before publication. (docs/RELEASING.md:31, 8fa910a7af64)
• Exact-head validation: The reviewed head has successful macOS, linux-read-core, Actions analysis, and JavaScript/TypeScript analysis checks; Swift analysis remains in progress, with no failed check reported. (8fa910a7af64)
• Established release ownership: Peter Steinberger authored repeated prior release preparations, including the same five-file metadata update for 0.20.0 in chore: prepare imsg 0.20.0 #369. (version.env:1, 5af52a029b3d)
• Feature-validation disclosure: The merged bodies of feat: mention people from send.rich and send.multipart #365, feat: place attached stickers on their bubble #366, and feat: set your Messages Name & Photo #377 explicitly describe fixture-based maintainer validation without live sends or account identity changes, supporting the release-note caveat. (CHANGELOG.md:9, 8fa910a7af64)

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 preparation with consistent metadata and no identified runtime defect.
• add rating: 🦐 gold shrimp: Overall readiness is 🦐 gold shrimp; proof is 🦐 gold shrimp 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 preparation with consistent metadata and no identified runtime defect.
• rating: 🦐 gold shrimp: Overall readiness is 🦐 gold shrimp; proof is 🦐 gold shrimp 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 5, 2026, 2:30 PM ET / 19:30 UTC.