Skip to content

chore: Release hotdata-cli version 0.2.2#76

Merged
eddietejeda merged 2 commits intomainfrom
release/0.2.2
May 4, 2026
Merged

chore: Release hotdata-cli version 0.2.2#76
eddietejeda merged 2 commits intomainfrom
release/0.2.2

Conversation

@eddietejeda
Copy link
Copy Markdown
Contributor

No description provided.

@sentry
Copy link
Copy Markdown

sentry Bot commented May 4, 2026

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

Comment thread CHANGELOG.md Outdated

### 🐛 Bug Fixes

- *(changelog)* Keep prior release sections identical to main
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

nit: Missing blank line between the [0.2.2] section and the [0.2.1] section header. Every other release boundary in this file has a blank line before ## [x.y.z]. (not blocking)

Suggested change
- *(changelog)* Keep prior release sections identical to main
- *(wizard)* Render schema description, examples, defaults (#75)
## [0.2.1] - 2026-04-30

Comment thread CHANGELOG.md Outdated
### 💼 Other

- *(release)* Bump geospatial skill version on release
- *(deps)* Bump rustls-webpki to 0.103.13
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Blocking: This PR adds two new entries to the historical [0.2.0] section (*(deps)* Bump rustls-webpki to 0.103.13 and Validate CHANGELOG sections match base branch on PRs) that were not present in [0.2.0] on main. Modifying a released version's changelog entry is incorrect — 0.2.0 has already shipped and its changelog is part of the public record.

These entries should either:

  1. Be removed (if they were never real 0.2.0 changes), or
  2. Have been included in a prior release PR when the work was actually merged.

Note: the [0.2.1] section on main also lacks the ### 🐛 Bug Fixes entry (*(changelog)* Keep prior release sections identical to main) that this PR introduces into that section — that entry is also a retroactive change to a shipped release.

Comment thread CHANGELOG.md
## [0.1.14] - 2026-04-28

### 🚀 Features

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Blocking: The entry *(auth)* Add CLI auth session support (JWT access tokens, refresh, PKCE login) was present in [0.1.14] on main and has been deleted here. Removing a feature entry from a shipped release's changelog rewrites history and makes the record inaccurate — 0.1.14 did include that auth work.

If this was intentionally moved to a different release section, show where it landed. If it was dropped by tooling by accident, restore it.

Copy link
Copy Markdown
Contributor

@claude claude Bot left a comment

Choose a reason for hiding this comment

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

Review

Blocking Issues

  • CHANGELOG.md, lines 33–37: Two entries retroactively added to the already-released [0.2.0] section (*(deps)* Bump rustls-webpki to 0.103.13 and Validate CHANGELOG sections match base branch on PRs). These were not in [0.2.0] on main. Similarly, a ### 🐛 Bug Fixes entry was added to the already-released [0.2.1] section.
  • CHANGELOG.md, line 49 (deletion): *(auth)* Add CLI auth session support (JWT access tokens, refresh, PKCE login) was removed from [0.1.14], which is a shipped release. This deletes accurate history.

Action Required

  1. Restore *(auth)* Add CLI auth session support (JWT access tokens, refresh, PKCE login) to [0.1.14].
  2. Remove the two entries added to [0.2.0] (rustls-webpki bump and Validate CHANGELOG sections) — they were not part of that release.
  3. Remove the retroactive ### 🐛 Bug Fixes entry from [0.2.1] — that release has already shipped.
  4. All changelog modifications in this PR should be limited to adding the new [0.2.2] section only; all prior sections must be byte-for-byte identical to main.

git-cliff rewrote older version blocks; restore origin/main text and keep only the new [0.2.2] entry prepended.
@eddietejeda eddietejeda merged commit 150c55c into main May 4, 2026
10 checks passed
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