Release 0.13.0 - #384
Merged
Merged
Conversation
Also consolidates the two `### Fixed` headings that merging #382 and #383 left in [Unreleased]. Both auto-merged cleanly and neither was wrong on its own; the result was a section with the heading twice, which publish.yml turns verbatim into the release notes. 🤖 Generated with [Claude Code](https://claude.com/claude-code)
![sourcery-ai[bot]](https://avatars.githubusercontent.com/in/48477?s=60&v=4){kind=small}
Reviewer's guide (collapsed on small PRs)Reviewer's GuideThis release PR promotes the accumulated behavioral changes and fixes to 0.13.0, cleans up the CHANGELOG structure, and synchronizes Cargo metadata, the lockfile, and README version references. File-Level Changes
Tips and commandsInteracting with Sourcery
Customizing Your ExperienceAccess your dashboard to:
Getting Help
|
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files
Flags with carried forward coverage won't be shown. Click here to find out more.
🚀 New features to boost your workflow:
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Releases the five review fixes merged today (#380, #381, #379, #382, #383) alongside the two entries already sitting in
[Unreleased](#347, #348).Minor rather than patch:
[Unreleased]carries behaviour changes, not just corrections — the SIGTERM/SIGHUP drain from #348 and the verdict cache from #382 both change what an existing workspace does.Contents
Changed — the public-API freeze is three snapshots instead of one (#347).
Fixed
killor a closed terminal now runs the same cleanup Ctrl-C does (SIGTERM and SIGHUP run the SIGINT drain #348)DEVLAUNCH_NO_ZELLIJ=1no longer stays without zellij forever (The verdict cache remembers which switches the pass ran under #382)Documentation-only, so not in the release notes: the herdr leftovers correction (#379), the
~/.claudemount Security Notes (#381) and the picker collision guard (#380, no user-visible behaviour beyond rows no longer being drawn a space apart).One thing this PR also fixes
Merging #382 and #383 left two
### Fixedheadings in[Unreleased]. Both auto-merged cleanly — GitHub reportedMERGEABLE/CLEANfor each — and neither insertion was wrong on its own; git simply placed them either side of### Changed.publish.yml:72-83turns that section verbatim into the GitHub release notes, so it would have shipped that way. The two blocks are consolidated here with all five bullets intact.Worth noting as a process point: a clean git merge is not the same as a coherent CHANGELOG, and nothing in CI checks the shape of that section.
Verified
cargo test --workspace: 1,677 passed, 0 failed.cargo fmt --checkclean.test_the_version_transcript_quotes_the_version_that_shipsandtest_the_conda_badge_names_the_version_that_ships, which is whyREADME.md:15(conda badge) andREADME.md:464(thedl --versiontranscript) move too. Previous release PRs touched three files; these two strings had been carried by the feature PR that happened to ship each release, and there is no such PR this time.rust/Cargo.lockrefreshed viacargo update -w, matching the shape of Release 0.6.0 #337/Release 0.7.2 #364/Release 0.10.0 #372/Release 0.11.0 #375.🤖 Generated with Claude Code
Summary by Sourcery
Release version 0.13.0 with consolidated changelog entries covering the latest workspace lifecycle and provisioning fixes.
Documentation:
Chores: