chore(deps): bump crossterm from 0.28.1 to 0.29.0 - #4
Merged
Conversation
hyperpolymath
commented
May 16, 2026
Owner
@dependabot rebase |
Bumps [crossterm](https://github.com/crossterm-rs/crossterm) from 0.28.1 to 0.29.0. - [Release notes](https://github.com/crossterm-rs/crossterm/releases) - [Changelog](https://github.com/crossterm-rs/crossterm/blob/master/CHANGELOG.md) - [Commits](https://github.com/crossterm-rs/crossterm/commits/0.29) --- updated-dependencies: - dependency-name: crossterm dependency-version: 0.29.0 dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
dependabotBotforce-pushed
the
dependabot/cargo/crossterm-0.29.0
branch
from
May 16, 2026 09:07
bc70714 to
333c70bComparehyperpolymath added a commit
that referenced
this pull request
Jul 27, 2026
…35) `cargo` cannot parse the lockfile on `origin/main`: ``` error: failed to parse lock file at: Cargo.lock Caused by: package `crossterm` is specified twice in the lockfile ``` It held **three** `crossterm` entries — `0.28.1`, `0.29.0`, `0.29.0`. Two *identical* versions is malformed; a package may appear more than once only at distinct versions. Introduced by `56dc58d` (#4, the crossterm 0.28.1→0.29.0 bump). Regenerated with `cargo generate-lockfile`. Resolution is now `0.28.1` (direct, per `Cargo.toml`s `crossterm = "0.28"`) plus `0.29.0` transitively — valid. **`cargo metadata` exits 0**, previously 101. Found while adding container packaging; reproduces with the host `cargo 1.97.1` outside any container, so it is not a packaging artefact. ## ⚠ This does not make the crate build A separate pre-existing breakage remains — the source does not compile against the resolved `ureq`: ``` error[E0599]: no method named `set` found for struct `RequestBuilder<B>` src/main.rs:66 error[E0599]: no variant named `Status` found for enum `ureq::Error` src/main.rs:70 ``` Both are **ureq 2.x APIs removed in 3.x** — a dependency bump landed without the source migration. Left for a separate change rather than bundled into a lockfile repair. ## What this implies Two dependency bumps merged — one breaking the source, one corrupting the lockfile — with nothing red enough to stop either. **This crate is not being compiled by CI.** 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-authored-by: Claude Opus 5 <noreply@anthropic.com>
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 freeto 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.
Bumps crossterm from 0.28.1 to 0.29.0.
Release notes
Sourced from crossterm's releases.
Changelog
Sourced from crossterm's changelog.
Commits