Tags: subinium/ezpn
Tags
ezpn v0.13.1 — clippy gate + RFC docs + split-pane cwd inheritance Patch release. Three workstreams: Strict clippy gate - Restored `-D warnings` (no `-A clippy::all` override) in both ci.yml and release.yml. v0.12.0 had relaxed it for deferred-wiring modules; v0.13.0 wired everything; the restore was promised for v0.12.1 (which we skipped). - Cleaned all surfaced warnings: field_reassign_with_default, useless_vec, dead_code in #[path]-mounted bench crates. Split-pane cwd inheritance (#75 final) - `do_split` now reads the focused pane's `live_cwd()` (OSC 7 reported cwd if fresh, else procfs, else launch-time cwd) and passes it to the new pane's spawn via `bootstrap::spawn_pane_in`. - Closes the v0.13.0 acceptance gap on issue #75. OSC 7 → procfs → launch-time resolution chain is now fully wired through new panes. Six RFC design docs - 0002 vt100 strategy commitment (#102) — soft-fork + upstream PRs in parallel, 4-week SLA per blocker. - 0003 IPC Ext channel routing (#103) — retroactive design doc for the IpcCommand::{Legacy, Ext} split that shipped in v0.13.0. - 0004 vt100-independent scrollback (#104) — byte-budget + sparse-row ScrollbackBuffer design. - 0005 memory budget SLA (#105) — per-pane / per-session / daemon RSS ceilings + CI gate plan. - 0006 snapshot v4 schema (#106) — named buffers + theme state + future-proof slots; v3 → v4 migration path. - 0007 OSC handler coverage matrix (#107) — full intercept/forward decision table across OSC 0/1/2/4/7/8/9/10/11/12/52/133. Issues closed - #75 OSC 7 cwd intercept (final acceptance gap) - #76 OSC 8 hyperlinks (verified pass-through in v0.13.0) - #77 OSC 4/10/11/12 (verified shipped in v0.13.0) - #102 #103 #104 #105 #106 #107 — RFC docs land Open after this release - #68 long-line scrollback (gated on RFC 0004 implementation) - #93 #94 #95 (v0.16.0 polish) - #99 (v1.0-rc perf regression suite) Tests: 397 + 25 unit + integration green. Strict clippy clean.
v0.13.0 — Multiplexer wiring + Memory & Persistence Roll-up release that finishes the v0.12.0 deferred-wiring backlog and opens the v0.13 design agenda. v0.12.1 was deliberately skipped — scope expanded past patch into user-visible features, justifying minor bump per SemVer. Wiring landed (14 issues closed): - #74 Kitty kbd flag replay on attach - #79 OSC 52 paste-injection guard with confirm-prompt UI - #80 status / tab-bar partial-redraw dirty producers - #82 events bus producers (11 sites) - #83 hooks fire sites (8/11 events) - #84 user-defined keymap dispatch (3 tables) - #85 theme system render integration - #86 fuzzy command palette + prefix-p binding - #87 status-bar contextual hints - #88 ezpn-ctl dump server handler - #89 ezpn-ctl ls --json server handler - #91 named copy buffers - #92 clipboard fallback chain - #71 scrollback eviction telemetry IPC architecture: - RFC #103 implemented — IpcCommand enum unifies Legacy + Ext channels. RFCs filed for v0.13+ design agenda: - #102 vt100 strategy commitment - #103 IPC Ext channel unification (executed) - #104 vt100-independent scrollback storage - #105 memory budget SLA + CI gate - #106 snapshot v4 schema - #107 OSC handler coverage matrix Stats: +2806 / -235 across 31 files. 397 main + 25 ezpn-ctl + 59 property tests passing.
ci: detect "already published" via cargo error, not crates.io API probe The previous curl check used `/api/v1/crates/ezpn/<version>` which isn't a 200 endpoint, so the guard always fell through to publish and hit `error: crate ezpn@0.8.0 already exists on crates.io index`. Switch to running `cargo publish` and inspecting its stderr — if it fails specifically with "already exists on crates.io", treat that as a no-op success. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
PreviousNext