Conversation
Greptile SummaryAutomated release PR generated by release-plz that bumps
No functional code changes are included — this is purely a version/metadata release. Safe to merge.
|
| 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
Last reviewed commit: a31203f
| ## [Unreleased] | ||
| ## [0.3.5] - 2026-03-14 |
There was a problem hiding this comment.
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.
| ## [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!
🤖 New release
gitv-tui: 0.3.4 -> 0.3.5 (✓ API compatible changes)Changelog
This PR was generated with release-plz.