chore(gitv-tui): release v0.3.3

[JayanAXHF]

🤖 New release

• gitv-tui: 0.3.2 -> 0.3.3 (✓ API compatible changes)

Changelog

[0.3.3] - 2026-03-04

Features

• (branding) Add a logo
• (nix) Add devshell, package derivation, flake

Bug Fixes

• Fix non-flake install instructions

Documentation

• Update usage in readme
• Add install instructions for homebrew

Performance

• Refactor the code to use interning and deduplication to reduce CPU usage by over 300%

Miscellaneous Tasks

• (release-plz) Add release-plz.toml
• (changelog) Add cliff.toml

---

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.2 to 0.3.3. The changes are limited to a version bump in Cargo.toml and Cargo.lock, plus a new changelog entry in CHANGELOG.md.

Key observations:

• Cargo.toml and Cargo.lock version bumps are correct and consistent.
• The CHANGELOG.md entry is missing a blank line between the [Unreleased] and [0.3.3] sections, which breaks the Keep a Changelog format.
• The [0.3.3] version heading is missing its comparison hyperlink (present on all prior version entries), suggesting the tooling may not have generated it correctly.
• The performance entry incorrectly states "reduce CPU usage by over 300%" — a percentage reduction cannot exceed 100%; the intent is likely a 3× or 4× improvement.

Important Files Changed

Filename	Overview
CHANGELOG.md	Adds the v0.3.3 changelog entry. Missing blank line between [Unreleased] and [0.3.3] sections, missing diff comparison hyperlink on the version heading, and an incorrect performance claim ("reduce CPU usage by over 300%").
Cargo.toml	Version bumped from 0.3.2 to 0.3.3. No other changes; straightforward and correct.
Cargo.lock	Lock file updated to reflect the new gitv-tui version 0.3.3. No dependency changes.

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A[release-plz triggers PR] --> B["Bump version in Cargo.toml\n0.3.2 to 0.3.3"]
    B --> C["Update Cargo.lock\ngitv-tui 0.3.3"]
    B --> D["Append CHANGELOG.md entry\nv0.3.3 - 2026-03-04"]
    D --> E1["Warning: Missing blank line\nbetween Unreleased and 0.3.3 sections"]
    D --> E2["Warning: No comparison URL\non 0.3.3 heading"]
    D --> E3["Warning: Invalid performance metric\n'reduce CPU usage by over 300%'"]
    C --> F["PR merged - crates.io publish"]
    E1 --> F
    E2 --> F
    E3 --> F

Loading

_{Last reviewed commit: f6f2dbf}

[greptile-apps]

Missing blank line between [Unreleased] and [0.3.3] sections

The ## [Unreleased] heading and ## [0.3.3] heading are placed on consecutive lines with no blank line separator. This deviates from the Keep a Changelog format (which the file header explicitly references) and can cause some Markdown renderers to fail to distinguish the two headings as separate sections.

Suggested change

	## [Unreleased]
	## [0.3.3] - 2026-03-04
	## [Unreleased]
	## [0.3.3] - 2026-03-04

[greptile-apps]

Missing diff comparison link on version heading

Every other version entry in this changelog includes a hyperlink to the GitHub comparison diff (e.g. [0.3.2](https://github.com/JayanAXHF/gitv/compare/gitv-tui-v0.3.1...gitv-tui-v0.3.2)), but the [0.3.3] heading does not. This likely means the link was not generated by release-plz or git-cliff as expected, making it harder for readers to view the exact diff for this release.

Suggested change

	## [0.3.3] - 2026-03-04
	## [0.3.3](https://github.com/JayanAXHF/gitv/compare/gitv-tui-v0.3.2...gitv-tui-v0.3.3) - 2026-03-04

[greptile-apps]

Misleading performance claim — CPU usage cannot be "reduced by over 300%"

A percentage reduction is bounded at 100% (eliminating the cost entirely). "Reduce CPU usage by over 300%" is not a valid metric — it likely means the CPU usage was reduced to roughly 1/4 of its original value (a ~75% reduction, or a ~4× speedup). Common correct phrasings would be:

• "reduce CPU usage by over 75%"
• "improve CPU performance by over 3×"
• "cut CPU usage to less than 1/3 of its original value"

Suggested change

	- Refactor the code to use interning and deduplication to reduce CPU usage by over 300%
	- Refactor the code to use interning and deduplication to improve CPU efficiency by over 3×