chore: release

[JayanAXHF]

🤖 New release

• ratatui-toaster: 0.1.1 -> 0.1.2 (✓ API compatible changes)
• gitv-tui: 0.3.4 -> 0.4.0 (✓ API compatible changes)

Changelog

ratatui-toaster

0.1.1 - 2026-02-22

Other

• (gitv-tui) release v0.3.0

gitv-tui

0.4.0 - 2026-03-20

Features

• (preview pane) Add a small issue list preview when in issue conversation
• (style) [breaking] Revamp the entire UI to have less borders and distractions

Bug Fixes

• fix test(ui): fix ui tests
• (md) fixed checklist rendering

Other

• cleanup fix(changelog): streamline changelog config in release-plz.toml
• Add dependabot.yml
• bump flake.lock, fix nitpick in drv, add .envrc

Testing

• test fix(benches): make benches use std::hint::black_box

---

This PR was generated with release-plz.

[greptile-apps]

Greptile Summary

This is an automated release PR generated by release-plz, bumping gitv-tui from 0.3.4 to 0.4.0 and ratatui-toaster from 0.1.1 to 0.1.2. The version bumps in Cargo.toml, crates/ratatui-toaster/Cargo.toml, and Cargo.lock are consistent and correct. The main concern is with the CHANGELOG.md entry for 0.4.0, which has a few issues worth addressing before tagging the release:

• Leaking sort-prefix tokens: Section headings contain raw <!-- N --> git-cliff ordering directives (e.g., ### <!-- 0 -->Features) that are not being stripped by the template. All prior release entries use clean headings, indicating a configuration regression introduced by the "streamline changelog config" commit.
• Missing blank line: No blank line separates the last bullet of the 0.4.0 section from the ## [0.3.4] header, inconsistent with every other version boundary in the file.
• Breaking change vs. "API compatible" label: The changelog itself marks the UI revamp as [**breaking**], but the PR description generated by release-plz labels the bump as "API compatible changes" — this discrepancy may confuse downstream consumers.

Important Files Changed

Filename	Overview
CHANGELOG.md	Adds the 0.4.0 release entry, but raw <!-- N --> sort-prefix tokens from git-cliff leak into section headings, a blank line is missing before the previous version header, and the entry contains a self-described breaking change despite the PR labelling the bump as "API compatible".
Cargo.toml	Version bumped from 0.3.4 to 0.4.0 and the ratatui-toaster path-dependency version constraint updated from 0.1.1 to 0.1.2. Changes look correct and consistent.
crates/ratatui-toaster/Cargo.toml	Patch version bump from 0.1.1 to 0.1.2. No other changes; looks correct.
Cargo.lock	Lock file updated to reflect the new versions of gitv-tui (0.4.0) and ratatui-toaster (0.1.2). No unexpected dependency changes observed.

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A([release-plz triggers PR]) --> B[Bump gitv-tui 0.3.4 → 0.4.0]
    A --> C[Bump ratatui-toaster 0.1.1 → 0.1.2]
    B --> D[Update Cargo.toml version]
    B --> E[Update ratatui-toaster dep constraint to 0.1.2]
    C --> F[Update crates/ratatui-toaster/Cargo.toml]
    D & E & F --> G[Regenerate Cargo.lock]
    G --> H[Append CHANGELOG.md entry for 0.4.0]
    H --> I{Heading format correct?}
    I -- No --> J[⚠️ Raw sort tokens in headings\ne.g. ### <!-- 0 -->Features]
    I -- Yes --> K[✅ Clean headings]
    H --> L{Blank line before prev version?}
    L -- No --> M[⚠️ Missing blank line\nbefore ## 0.3.4]
    L -- Yes --> N[✅ Proper spacing]

Loading

_{Last reviewed commit: "chore: release"}