Skip to content

chore(deps): bump tuika to 0.8.0 with matching satellite crates - #563

Open
chaliy wants to merge 1 commit into
mainfrom
chore/bump-tuika-0.8-group
Open

chore(deps): bump tuika to 0.8.0 with matching satellite crates#563
chaliy wants to merge 1 commit into
mainfrom
chore/bump-tuika-0.8-group

Conversation

@chaliy

@chaliy chaliy commented Aug 13, 2026

Copy link
Copy Markdown
Contributor

What changed

Bumps tuika 0.7.0 → 0.8.0 together with the satellite crates that must move in lockstep (tuika-codeformatters 0.4.1, tuika-mermaid 0.2.1, tuika-html 0.1.1), plus the unrelated patch bumps bundled in dependabot's cargo-minor-and-patch group (ast-grep-core/language, async-trait, base64, clap, ignore, tree-sitter, tree-sitter-scala). No functional/behavior change — dependency versions only.

Supersedes dependabot's #559 and #560, which each fail CI when applied alone.

Why

tuika-codeformatters 0.4.1 (and the other satellites) require tuika 0.8. Dependabot split the family across two PRs — #560 bumped tuika alone, #559 bumped the satellites alone — and each leaves two incompatible tuika versions in the dependency graph, which fails to compile:

error[E0277]: the trait bound `tuika_codeformatters::TreeSitterHighlighter: tuika::highlight::Highlighter` is not satisfied
  --> src/main.rs:1126:57
note: there are multiple different versions of crate `tuika` in the dependency graph

Bumping the whole family together in one cargo update resolves it.

Before / After

No observable behavior change — this is a dependency-version-only bump (Cargo.toml/Cargo.lock). Evidence is build/test success rather than a before/after CLI diff:

Risk

  • Low
  • What can break: tuika 0.8.0 adds new components (AppShell, KeyedTable, SelectionScreen, etc.) but yolop doesn't use them yet; the full test suite (including tests/tuika_pty.rs PTY-driven rendering tests) passed unchanged, so no rendering regression was observed locally.

Checklist

  • Tests added or updated — n/a, dependency bump only; existing suite re-verified
  • Backward compatibility considered — yolop is pre-1.0, tuika is a normal crates.io dependency
  • Knowledge concepts updated, or no update required with a reason — see Knowledge

Knowledge

No knowledge update required — routine dependency bump, no behavior/architecture/policy change.

Security

No security-relevant code changes — this only updates Cargo.toml/Cargo.lock pins for existing dependencies to versions dependabot already proposed independently; no new crates, no code touched.

Follow-ups

No follow-ups.

tuika-codeformatters 0.4.1, tuika-mermaid 0.2.1, and tuika-html 0.1.1 all
require tuika 0.8; bumping any of them alone (as dependabot's separate PRs
#559 and #560 each did) leaves two incompatible `tuika` versions in the
dependency graph and fails to compile (TreeSitterHighlighter no longer
implements Highlighter). Bumping the whole family together in one lockfile
update resolves it. Also picks up the unrelated cargo-minor-and-patch group
bumps from #559 (ast-grep, async-trait, base64, clap, ignore, tree-sitter,
tree-sitter-scala) since they were bundled in the same dependabot group.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant