Skip to content

feat: add release-notes command - #127

Closed
marcus wants to merge 1 commit into
mainfrom
feature/release-notes-drafter-v4
Closed

marcus wants to merge 1 commit into
mainfrom
feature/release-notes-drafter-v4

Conversation

@marcus

@marcus marcus commented Apr 11, 2026 •

Copy link
Copy Markdown
Owner

Summary

  • add a built-in td release-notes command that drafts changelog-ready markdown from local git history
  • add git helpers and release-note classification/rendering coverage for tag ranges, docs-only commits, and empty output
  • fix default --to handling so explicit commit SHAs or branch refs on tagged commits do not walk back past the latest release tag

Testing

  • go test ./internal/git ./internal/releasenotes ./cmd
  • go test ./...
  • go run . release-notes --from v0.43.0 --to HEAD --version vNEXT | head -n 20

Supersedes the earlier release-notes iteration with the explicit --to <sha> tagged-commit regression fixed.


Automated by nightshift

Nightshift-Task: release-notes
Nightshift-Ref: https://github.com/marcus/nightshift
@marcus

marcus commented Aug 27, 2026

Copy link
Copy Markdown
Owner Author

Closing as a duplicate. An automated agent opened 18 separate PRs for the same changelog / release-notes drafting command between March and May 2026. Keeping #176 as the single representative; closing the rest unreviewed.

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