* Render mail print metadata as text and isolate print documents
* Update application dependencies for published security advisories
* Require patched Dovecot and Pigeonhole in mail images
* fix(security): pin patched Node and Bun runtimes across releases
* fix(build): pass bootstrap selection independently of eval arguments
* test(build): expect the patched default Bun image in detection
* docs: prepare 0.9.4 changelog since 0.9.3
Route API, platform, deployment, background, Desktop, CLI and browser failures through a bounded redacting reporter with request and operation correlation. Preserve operation behavior and provider-specific credential sanitizers.
Add public browser intake, safe exporter and shutdown behavior, coverage audits in CI and release gates, and regression tests for correlation, privacy, stream semantics, backpressure and real API/browser delivery.
Release tags are lightweight, so the workflow's `gh release create
--notes-from-tag` had nothing to read beyond the "Bump to vX.Y.Z" commit
subject: every GitHub Release shipped with an effectively empty
description, and release watchers saw no notes (oblien/openship#192).
scripts/changelog-notes.ts (zero-dep, node:-only) extracts the version's
level-2 section from CHANGELOG.md: exact version match (0.6.1 never
matches 0.6.10), tolerant of `v`/bracketed/dated headings, bounded by
the next version heading. Missing section falls back to a changelog
link; a prerelease with no own section borrows the base version's notes
with a prerelease preamble; bodies are cut at 120k chars on a line
boundary. Every path returns a body: notes can never fail a release.
The publish job writes the notes to a file and passes --notes-file
(never shell-interpolated: changelog prose is full of backticks), and
on re-runs backfills only releases whose body is empty, so hand-edited
release pages are never overwritten. The docker-only path creates no
release and is untouched. release.ts now surfaces the resolved notes
state in its pre-flight summary so a missing section is visible before
the tag is pushed.
Tests (bun test, wired into the root test script as test:scripts) cover
section bounding, version prefix collisions, fallback and prerelease
borrowing, truncation, and extraction against the real CHANGELOG.md.