chore: release

[JayanAXHF]

🤖 New release

• ratatui-toaster: 0.1.2 -> 0.1.3
• gitv-tui: 0.4.2 -> 0.4.3

Changelog

ratatui-toaster

0.1.3 - 2026-04-19

Miscellaneous Tasks

• release

gitv-tui

0.4.3 - 2026-04-19

Other

• (ci) add cargo-machete ci job

Miscellaneous Tasks

• fix clippy lints

---

This PR was generated with release-plz.

[greptile-apps]

Greptile Summary

This is an automated release PR generated by release-plz, bumping ratatui-toaster from 0.1.2 → 0.1.3 and gitv-tui from 0.4.2 → 0.4.3. The only file changed in the diff is crates/ratatui-toaster/CHANGELOG.md, which adds the 0.1.3 entry.

• The changelog skips v0.1.2 entirely — the history goes 0.1.1 → 0.1.3, leaving no record of what changed in the 0.1.2 release that this PR claims to supersede.

Important Files Changed

Filename	Overview
crates/ratatui-toaster/CHANGELOG.md	Adds v0.1.3 release entry; missing v0.1.2 entry breaks changelog continuity from 0.1.1 → 0.1.3

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A["release-plz triggers release PR"] --> B["Bump ratatui-toaster 0.1.2 → 0.1.3"]
    A --> C["Bump gitv-tui 0.4.2 → 0.4.3"]
    B --> D["Append entry to crates/ratatui-toaster/CHANGELOG.md"]
    C --> E["gitv-tui changelog (not in this diff)"]
    D --> F{"0.1.2 entry present?"}
    F -- "No (gap)" --> G["⚠️ Changelog skips 0.1.1 → 0.1.3"]
    F -- "Yes" --> H["✅ Continuous history"]

Loading

_{Reviews (1): Last reviewed commit: "chore: release" | Re-trigger Greptile}

[greptile-apps]

Missing 0.1.2 changelog entry

The changelog jumps from 0.1.1 directly to 0.1.3, skipping 0.1.2. The PR description states this release bumps ratatui-toaster from 0.1.2 → 0.1.3, implying 0.1.2 was a previously published version — but there is no corresponding entry in this file. If 0.1.2 was released, its changes should be documented here to maintain an accurate history for downstream consumers.

[greptile-apps]

Raw HTML comment in section heading

The section heading ### <!-- 7 -->Miscellaneous Tasks contains a literal HTML comment that will be invisible in most Markdown renderers, but is visible in raw file views (e.g. GitHub's "Raw" button, cat, editors). Most changelog viewers and crate registries (docs.rs, crates.io) will render it cleanly, but it may look odd in diff views or plain-text tooling. If this is intentional release-plz ordering syntax, it can be left as-is — otherwise the comment should be stripped.

Suggested change

	### <!-- 7 -->Miscellaneous Tasks
	### Miscellaneous Tasks