chore(deps): bump rio-vt from 0.5.25 to 0.5.26

[dependabot]

Bumps rio-vt from 0.5.25 to 0.5.26.

Release notes

Sourced from rio-vt's releases.

v0.5.26

Full Changelog: https://rioterm.com/changelog

Commits

• 8e7cb9e add rio-grid readme
• b36815a add 0.5.26 metainfo release entry
• f5d4fef prepare v0.5.26
• 761f5a5 fix fmt
• 1106bb8 update test
• 21082c0 reset style change
• fcb619c update lock
• 599524f reorg
• 4ddaa22 novel system
• 0cfe201 wip
• Additional commits viewable in compare view

[github-actions]

Thanks @dependabot[bot] for taking the time to contribute.

This repository is observing a maintainer-managed PR intake gate in dry-run mode, so this pull request is staying open. This note helps maintainers prepare the allowlist before any enforcement is considered.

Please read CONTRIBUTING.md for the expected contribution shape. A maintainer can grant recurring PR access by commenting /lgtm on a pull request.

[Hmbown]

Thanks @dependabot — this one needs a small source change alongside the lock bump, so leaving it open rather than rebasing.

All three reds (Lint, Test ubuntu-latest, Test macos-latest on run 33230921708) are the same compile error: error[E0616]: field 'style_set' of struct 'rio_vt::crosswords::grid::Grid' is private. rio-vt 0.5.26 made Grid.style_set private and added pub fn styles(&self) -> &[Style] (rio-vt/src/crosswords/grid/mod.rs:716 at tag v0.5.26; it was pub style_set at :74 in v0.5.25). The change is not called out in the release notes.

Exact fix, three lines in crates/tui/tests/support/qa_harness/frame.rs (:166, :173, :192):

-        let styles = self.term.grid.style_set.styles();
+        let styles = self.term.grid.styles();

Same &[Style] return type, so square_colors(square, styles) is unchanged, and nothing else in the tree references style_set. Note that frame.rs is compiled only under #[cfg(all(unix, feature = "long-running-tests"))] (crates/tui/tests/cucumber/plugin_e2e_acceptance.rs:18), so verify with cargo check -p codewhale-tui --tests --all-features on macOS or Linux — the Windows pass on this run is not evidence.

Plan: a maintainer branch carrying cargo update -p rio-vt --precise 0.5.26 plus that edit will supersede this PR; this will be closed with a link when that lands.

[Hmbown]

Maintainer fix branch for this bump is up: fix/rio-vt-0.5.26-qa-harness-20260830 @ e3cc1a45fa432423b26cb7a3235520f20072f422 (this PR's lock bump 7a71d57380 merged with main, plus the three-line frame.rs change from the receipt above — self.term.grid.style_set.styles() → self.term.grid.styles() at :166, :173, :192).

Confirmed against the 0.5.26 crate source in the registry: Grid.style_set is private (src/crosswords/grid/mod.rs:83) and pub fn styles(&self) -> &[Style] is at :716; square_colors(square, styles) already takes &[Style], so nothing else changes.

Proof on macOS (the harness is compiled only under #[cfg(all(unix, feature = "long-running-tests"))], and it lives in the consolidated cucumber test target):

$ cargo test -p codewhale-tui --test cucumber --features long-running-tests --no-run
    Finished `test` profile [unoptimized + debuginfo] target(s) in 2m 53s
  Executable tests/cucumber/main.rs (target/debug/deps/cucumber-9cefaf79f65d85db)

$ cargo check -p codewhale-tui --all-targets
    Finished `dev` profile [unoptimized + debuginfo] target(s) in 1m 53s

$ cargo check -p codewhale-tui --tests --all-features
    Finished `dev` profile [unoptimized + debuginfo] target(s) in 1m 50s

Negative control with the fix stashed, same gated command: the same three error[E0616]: field style_setof structrio_vt::crosswords::grid::Grid is private at frame.rs:166:37, :173:37, :192:37 that CI reported, so the gate does exercise the file.

A maintainer will land this via the fix branch. Dependabot's branch cannot take a non-force push from us and we do not force-push, so this PR will be closed with a link once the branch merges.

[dependabot]

OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version or @dependabot ignore this minor version. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.