Skip to content

chore(tui-widgets): release v0.7.5#259

Merged
joshka merged 1 commit into
mainfrom
release-plz-tui-widgets-2026-06-11T23-52-31Z
Jun 12, 2026
Merged

chore(tui-widgets): release v0.7.5#259
joshka merged 1 commit into
mainfrom
release-plz-tui-widgets-2026-06-11T23-52-31Z

Conversation

@github-actions

@github-actions github-actions Bot commented Jun 11, 2026

Copy link
Copy Markdown
Contributor

🤖 New release

  • tui-widgets: 0.7.4 -> 0.7.5 (✓ API compatible changes)
Changelog

[0.7.5] - 2026-06-11

📚 Documentation

  • (scrollbar) Improve API discovery (#251)

    Summary

    • Improve tui-scrollbar crate docs for API discovery, styling
      behavior, glyph selection, and interaction flow.
    • Add a small scrollbar_styled example that shows distinct track,
      thumb, and arrow styles for vertical and horizontal scrollbars.
    • Configure docs.rs example scraping and add a regression test for
      custom thumb styling on full and partial thumb cells.

    Details

    This is a non-functional docs/examples/tests change. It reorganizes the
    crate-level docs so important defaults and caveats are visible earlier,
    replaces the loose ScrollBar “Key methods” list with a grouped method
    map, and adds canonical examples for the main builder methods.

    The styling docs now spell out how fg and bg apply to terminal glyph
    cells. In particular, they call out that the default minimal track
    renders spaces, so empty track cells show background color, while
    visible glyph sets can use foreground color for the track line. The docs
    also note the partial-thumb caveat: when using visible tracks such as
    GlyphSet::box_drawing, thumb background can show at partial glyph
    edges, so matching it to the track background is usually less
    surprising.

    The glyph docs keep repeated Symbols for Legacy Computing context
    where readers may land directly, rather than relying on linear reading
    through the crate docs.

    Related context:

    Validation

    • cargo test -p tui-scrollbar --all-features
    • cargo test -p tui-scrollbar --doc --all-features
    • cargo check -p tui-scrollbar --examples --all-features
    • cargo clippy -p tui-scrollbar --all-targets --all-features
    • RUSTDOCFLAGS='-D warnings' cargo doc -p tui-scrollbar --no-deps --all-features
    • just fmt-check
    • cargo rdme --check --manifest-path tui-scrollbar/Cargo.toml
    • markdownlint-cli2 tui-scrollbar/README.md

⚙️ Miscellaneous Tasks

  • (tui-scrollbar) Release v0.2.6 (#258)

    🤖 New release

    • tui-scrollbar: 0.2.5 -> 0.2.6 (✓ API compatible changes)
    Changelog

    [0.2.6] - 2026-06-11

    📚 Documentation

    • (scrollbar) Improve API discovery
      (#251)

      Summary

      • Improve tui-scrollbar crate docs for API discovery, styling
        behavior, glyph selection, and interaction flow.
      • Add a small scrollbar_styled example that shows distinct track,
        thumb, and arrow styles for vertical and horizontal scrollbars.
      • Configure docs.rs example scraping and add a regression test for
        custom thumb styling on full and partial thumb cells.

      Details

    This is a non-functional docs/examples/tests change. It reorganizes
    the
    crate-level docs so important defaults and caveats are visible
    earlier,
    replaces the loose ScrollBar “Key methods” list with a grouped
    method
    map, and adds canonical examples for the main builder methods.

    The styling docs now spell out how fg and bg apply to terminal
    glyph
    cells. In particular, they call out that the default minimal track
    renders spaces, so empty track cells show background color, while
    visible glyph sets can use foreground color for the track line. The
    docs
    also note the partial-thumb caveat: when using visible tracks such as
    GlyphSet::box_drawing, thumb background can show at partial glyph
    edges, so matching it to the track background is usually less
    surprising.

    The glyph docs keep repeated Symbols for Legacy Computing context
    where readers may land directly, rather than relying on linear reading
    through the crate docs.

    Related context:

    Validation

    • cargo test -p tui-scrollbar --all-features
    • cargo test -p tui-scrollbar --doc --all-features
    • cargo check -p tui-scrollbar --examples --all-features
    • cargo clippy -p tui-scrollbar --all-targets --all-features
    • RUSTDOCFLAGS='-D warnings' cargo doc -p tui-scrollbar --no-deps --all-features
    • just fmt-check
    • cargo rdme --check --manifest-path tui-scrollbar/Cargo.toml
    • markdownlint-cli2 tui-scrollbar/README.md


    This PR was generated with
    release-plz.


This PR was generated with release-plz.

@github-actions github-actions Bot force-pushed the release-plz-tui-widgets-2026-06-11T23-52-31Z branch from 71798e2 to 2233231 Compare June 11, 2026 23:56
@joshka joshka enabled auto-merge (squash) June 12, 2026 00:01
@codecov-commenter

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 87.65%. Comparing base (b5aaa4f) to head (2233231).

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #259   +/-   ##
=======================================
  Coverage   87.65%   87.65%           
=======================================
  Files          22       22           
  Lines        4237     4237           
=======================================
  Hits         3714     3714           
  Misses        523      523           

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

@joshka joshka merged commit e743a49 into main Jun 12, 2026
25 checks passed
@joshka joshka deleted the release-plz-tui-widgets-2026-06-11T23-52-31Z branch June 12, 2026 00:03
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.

2 participants