Repository navigation
Bump to 0.11.5 - #24
Conversation
The two commits between v0.11.4 and here were squash merges whose messages carry no `Release notes:` bullet, which is what script/draft-release-notes reads, so 0.11.5 would have shipped with the generic placeholder body. Supplying them here instead. Cargo.lock was also stale on main: #23 added `util` to dez_sidebar, and CI verifies the build without committing the lock, so the resolved dependency never landed. `cargo metadata --offline` picks it up without compiling. Release notes: - Added a search field to the workspace rail that filters by workspace name, session title, agent kind, and working directory, highlighting matches in place. Bound to `cmd-f` / `ctrl-f`. - Fixed closed agent sessions lingering in the workspace rail, agent sessions showing a stale status after their process exited, and rail session rows failing to focus silently.
|
Important
This repository does not receive automatic reviews because it has fewer than 10 stars. ⚙️ Run configuration
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
![graphify-labs[bot]](https://avatars.githubusercontent.com/in/4356270?s=60&v=4){kind=small}
There was a problem hiding this comment.
Graphify reviewed this change.
Looks safe to merge — no coupling regressions and no blocking issues, checked against the code graph (not a self-assessment).
Graphify review — findings
Bumps dez from 0.11.4 to 0.11.5 and records a new util dependency in Cargo.lock for a workspace crate that already depends on settings, ui, and workspace.
No blocking issues surfaced.
Analysis details — impact, health, verification
Impact & health
Graphify review
Impact — 0 functions depend on the 0 functions this change touches.
Health — grade A; no new coupling hotspots.
Verification — 0 functions in the blast radius were not formally verified this run (proofs are advisory here).
Gate & verification
graphify gate
PASS — objectively clean (no health regressions, tests not run — proofs not run this pass (advisory)). Grounded, not self-assessed.
1 participant
Summary
Version bump for the stable release, plus two corrections that would otherwise have shipped broken:
Cargo.lockwas stale onmain. Make the rail's view of terminal-backed sessions truthful #23 addedutiltocrates/dez_sidebar/Cargo.toml, and CI verifies the build without committing the lock, so the resolved dependency never landed. Caught bycargo metadata --offline(no compile).v0.11.4carries aRelease notes:bullet, which is the only thingscript/draft-release-notesreads, so 0.11.5 would have gone out with the generic body. They are supplied on the bump commit, which is where the script will find them.crates/dez/RELEASE_CHANNELstaysstable, so the tag is a plainv0.11.5with no suffix —script/determine-release-channelrejects-pretags on the release job.Merging this does not create the release. The tag is pushed separately once this lands, and
release.ymlcreates the draft, runs the suite, builds the assets, and publishes.Per
AGENTS.md, a version-only diff can merge on the fast checks (clippy,fmt,build-linux) without waiting on the ~45 mintestsjob, sincerelease.ymlre-runs the suite against the tag before building assets.Rules
Release Notes: