Skip to content

Refresh the 0.16.0 release notes for master at 4a05edb3 - #3362

Merged
erskingardner merged 3 commits into
masterfrom
release/0.16.0-metadata-refresh
Nov 12, 2026
Merged

erskingardner merged 3 commits into
masterfrom
release/0.16.0-metadata-refresh

Conversation

@erskingardner

@erskingardner erskingardner commented Nov 12, 2026 •

Copy link
Copy Markdown
Member

Problem

The 0.16.0 notes (#3320) were written two days before the release, and 36 commits have landed since. Those commits include the OpenMLS security fixes, shared NIP-46 sessions, and a fix for chats that silently stopped receiving messages. The release tags current master, so the notes must describe it.

Fix

This folds every Unreleased changelog entry into 0.16.0, dates it 2026-11-12 and drops the test-only #3323 entry. It adds Fixed entries for #3349, #3358, #3345, #3330, #3314 and #3313 and updates the upgrade guide's provenance to 4a05edb3 (72 commits after v0.15.0). The release notes and upgrade guide now sort these changes into the required/default/optional/automatic categories. The guide also corrects an existing error: it said no MarmotKitError case was added, but #3303 adds Nip46.

Verification

  • Local: just release-pr-preflight 0.16.0 (release-PR exception; no build or tests)
  • Review: Codex gpt-6.1-sol and Cursor grok-4.7-high-fast recommend merge at fa261f7

Classification notes

🤖 Generated with Claude Code

erskingardner and others added 3 commits November 12, 2026 08:26
Fold the post-#3320 Unreleased entries into 0.16.0, date it 2026-11-12,
drop the test-only #3323 entry, and add user-visible fixes that had no
entry (#3333, #3342, #3345, #3330, #3290, #2760). Cover OpenMLS's
security fixes, shared NIP-46 sessions, media replies and the Hermes file
modes in the release notes and upgrade guide, and correct the guide's
claim that no MarmotKitError case is added.

Co-Authored-By: Claude Opus 5.5 <[email protected]>
Cancel keeps stored credentials and the next start restores the session;
logout, remove, sign-out and wipe erase the communication key. List the
C status record's has_last_error and generation fields.

Co-Authored-By: Claude Opus 5.5 <[email protected]>
@coderabbitai

coderabbitai Bot commented Nov 12, 2026

Copy link
Copy Markdown
Contributor

Warning

Review limit reached

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

Next included review available in 32 minutes.

Check out review usage here.

View limit details

Limit details: You’ve used the included review currently available. Your 87 included PR review attempts over the past 7 days set your current allowance at 1 review per hour.

Learn how review limits work.

Review configuration:

Run configuration

  • Source mode: Auto
  • Repository: Unavailable
  • Branch: Unavailable
  • File: No configuration file from this repository applied
  • Commit: Unavailable
  • Layers: Organization UI
  • Review profile: CHILL
  • Plan: Team
  • Run ID: 682dea2e-18a8-4691-b064-2a95bf5abc45
Commits

Reviewing files that changed from the base of the PR and between 4a05edb and fa261f7.

Files selected for processing: 10

  • CHANGELOG.md
  • crates/cgka-engine/CHANGELOG.md
  • crates/cli/CHANGELOG.md
  • crates/marmot-app/CHANGELOG.md
  • crates/marmot-c/CHANGELOG.md
  • crates/marmot-uniffi/CHANGELOG.md
  • crates/storage-sqlite/CHANGELOG.md
  • crates/traits/CHANGELOG.md
  • docs/integration/0.16.0.md
  • docs/release/0.16.0.md
  • Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

@erskingardner
erskingardner added this pull request to the merge queue Nov 12, 2026
Merged via the queue into master with commit a2e0558 Nov 12, 2026
38 checks passed
@erskingardner
erskingardner deleted the release/0.16.0-metadata-refresh branch November 12, 2026 09:30
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