release: 0.57.1 - #654
Merged
Merged
release: 0.57.1#654
Conversation
dl <ws> rm no longer refuses over commits the remote holds as new commits (#653). After a rebase, a cherry-pick or a squash merge the old commits are on no remote ref, so the guard and dl --ls --json counted them as unpushed. A commit whose exact change is on a compared remote ref, confirmed by git merge-tree, no longer counts, and nor does a merge that adds nothing to its parents. The picker no longer panics when TERM names no usable terminal (#647). No public API changed, so this is a patch bump. All four copies of the version move together: Cargo.toml, Cargo.lock, and the README conda badge and dl --version transcript.
Reviewer's guide (collapsed on small PRs)Reviewer's GuideThis patch-release PR contains no implementation or public API changes; it versions the five Rust workspace crates and lockfile as 0.57.1, updates README release references, and finalizes the changelog for the two fixes already present on main. Review should focus on version consistency, changelog accuracy, and ensuring the lockfile diff is limited to the expected package-version updates. File-Level Changes
Tips and commandsInteracting with Sourcery
Customizing Your ExperienceAccess your dashboard to:
Getting Help
|
![sourcery-ai[bot]](https://avatars.githubusercontent.com/in/48477?s=60&v=4){kind=small}
There was a problem hiding this comment.
Hey - I've found 1 issue
Prompt for AI Agents
Please address the comments from this code review:
## Individual Comments
### Comment 1
<location path="CHANGELOG.md" line_range="14" />
<code_context>
### Fixed
-- **`rm` no longer refuses over commits the remote holds as new commits.** After a
+- **`rm` no longer refuses over commits the remote holds as new commits** (#653). After a
rebase, a cherry-pick or a squash merge, the old commits are on no remote ref, so
`rm` and `dl --ls --json` counted them as unpushed although nothing in them was
</code_context>
<issue_to_address>
**nitpick:** The changelog claims to add links to PRs, but `#653` and `#647` are plain text rather than Markdown links, so readers cannot follow either issue directly from the release notes.
**Suggested fix:** Use links such as `[#653](https://github.com/blooop/devlaunch/pull/653)` and `[#647](https://github.com/blooop/devlaunch/pull/647)`.
</issue_to_address>| ### Fixed | ||
|
|
||
| - **`rm` no longer refuses over commits the remote holds as new commits.** After a | ||
| - **`rm` no longer refuses over commits the remote holds as new commits** (#653). After a |
There was a problem hiding this comment.
nitpick: The changelog claims to add links to PRs, but #653 and #647 are plain text rather than Markdown links, so readers cannot follow either issue directly from the release notes.
Suggested fix: Use links such as [#653](https://github.com/blooop/devlaunch/pull/653) and [#647](https://github.com/blooop/devlaunch/pull/647).
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.
This release is a patch release, 0.57.1. It ships two fixes that are on
main:dl <ws> rmanddl --ls --jsonno longer count a commit whose exact change is already on a compared remote ref, or a merge that adds nothing of its own.TERMnames no usable terminal.No public API changed, so this is a patch bump.
What this changes
rust/Cargo.tomlandrust/Cargo.lock: the five workspace crates go from 0.57.0 to 0.57.1.cargo update -w --offlinewrote the lock file.README.md: the conda badge and thedl --versiontranscript say 0.57.1.CHANGELOG.md: the[Unreleased]entries move under[0.57.1] - 2026-09-29, with links to their PRs.How I checked it
cargo build --locked -p dl, thendl --version: it printeddl 0.57.1.pixi run test: 828 passed. That includes the README guard.prekon the four changed files: clean.🤖 Generated with Claude Code
Summary by Sourcery
Release version 0.57.1 with the latest fixes and updated project version references.
Build:
Documentation: