Skip to content

chore(gitv-tui): release v0.3.5#89

Open
JayanAXHF wants to merge 1 commit intomainfrom
release-plz-2026-03-14T12-59-03Z
Open

chore(gitv-tui): release v0.3.5#89
JayanAXHF wants to merge 1 commit intomainfrom
release-plz-2026-03-14T12-59-03Z

Conversation

@JayanAXHF
Copy link
Owner

🤖 New release

  • gitv-tui: 0.3.4 -> 0.3.5 (✓ API compatible changes)
Changelog

[0.3.5] - 2026-03-14

Other

  • Bump flake.lock, fix nitpick in drv, add .envrc


This PR was generated with release-plz.

@greptile-apps
Copy link
Contributor

greptile-apps bot commented Mar 14, 2026

Greptile Summary

Automated release PR generated by release-plz that bumps gitv-tui from v0.3.4 to v0.3.5. The changes are minimal and mechanical:

  • Cargo.toml: version field updated to 0.3.5
  • Cargo.lock: auto-generated lockfile reflects the new version
  • CHANGELOG.md: new v0.3.5 entry documenting the flake.lock bump, Nix derivation fix, and .envrc addition

No functional code changes are included — this is purely a version/metadata release. Safe to merge.

Important Files Changed

Filename Overview
Cargo.toml Version bump from 0.3.4 to 0.3.5 — single-line change, no issues.
Cargo.lock Auto-generated lockfile version bump from 0.3.4 to 0.3.5, no issues.
CHANGELOG.md New v0.3.5 changelog entry added; minor pre-existing formatting inconsistency (missing blank line before previous section heading) but consistent with prior entries.

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A["release-plz trigger"] --> B["Bump version in Cargo.toml\n0.3.4 → 0.3.5"]
    B --> C["Update Cargo.lock"]
    B --> D["Add CHANGELOG.md entry\nfor v0.3.5"]
    C --> E["Release PR #89"]
    D --> E
Loading

Last reviewed commit: a31203f

Comment on lines 8 to +9
## [Unreleased]
## [0.3.5] - 2026-03-14
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Missing blank line after [Unreleased]
The ## [Unreleased] heading runs directly into ## [0.3.5] with no blank line separating them. Per the Keep a Changelog format, each section should be separated by a blank line. This is a pre-existing pattern in your changelog (the same thing happens between v0.3.5 and v0.3.4 on lines 13-14), but it may be worth fixing to keep the document well-structured.

Suggested change
## [Unreleased]
## [0.3.5] - 2026-03-14
## [Unreleased]
## [0.3.5] - 2026-03-14

Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!

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.

1 participant