chore(deps): bump tuika to 0.8.0 with matching satellite crates - #563
Open
chaliy wants to merge 1 commit into
Open
chore(deps): bump tuika to 0.8.0 with matching satellite crates#563chaliy wants to merge 1 commit into
chaliy wants to merge 1 commit into
Conversation
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.
This was referenced Aug 13, 2026
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
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.
What changed
Bumps
tuika0.7.0 → 0.8.0 together with the satellite crates that must move in lockstep (tuika-codeformatters0.4.1,tuika-mermaid0.2.1,tuika-html0.1.1), plus the unrelated patch bumps bundled in dependabot'scargo-minor-and-patchgroup (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-codeformatters0.4.1 (and the other satellites) requiretuika0.8. Dependabot split the family across two PRs — #560 bumpedtuikaalone, #559 bumped the satellites alone — and each leaves two incompatibletuikaversions in the dependency graph, which fails to compile:Bumping the whole family together in one
cargo updateresolves 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:
cargo build --all-features: succeeds (previously failed to compile with the partial bump, per chore(deps): bump the cargo-minor-and-patch group with 11 updates #559/chore(deps): bump tuika from 0.7.0 to 0.8.0 #560 CI logs above)cargo test --all-features: 1065 + 58 + 1 + 5 tests, 0 failedRisk
tests/tuika_pty.rsPTY-driven rendering tests) passed unchanged, so no rendering regression was observed locally.Checklist
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.lockpins for existing dependencies to versions dependabot already proposed independently; no new crates, no code touched.Follow-ups
No follow-ups.