Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore: Add template for grouping BREAKING CHANGES to the top #5964

Merged
merged 1 commit into from
Aug 23, 2024

Conversation

mofojed
Copy link
Member

@mofojed mofojed commented Aug 21, 2024

  • Also added a cog.toml file
  • Just run cog changelog to generate the full changelog
  • For between two tags/commits, add the range as an arg, e.g. cog changelog v0.35.0..v0.36.0
  • Generates a changelog file with the text from the Breaking Changes footers at the top

- Also added a cog.toml file
- Just run `cog changelog` to generate the full changelog
- For between two tags/commits, add the range as an arg, e.g. `cog changelog v0.35.0..v0.36.0`
- Generates a changelog file with the text from the Breaking Changes footers at the top
@mofojed mofojed requested a review from devinrsmith August 21, 2024 19:59
@mofojed mofojed self-assigned this Aug 21, 2024
@mofojed mofojed added NoDocumentationNeeded NoReleaseNotesNeeded No release notes are needed. labels Aug 21, 2024
Copy link
Member

@devinrsmith devinrsmith left a comment

Choose a reason for hiding this comment

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

LGTM. We should probably follow up with updates to RELEASE.md to describe procedure to generate release notes.

@mofojed mofojed merged commit 8fb1bc7 into deephaven:main Aug 23, 2024
18 of 20 checks passed
@mofojed mofojed deleted the cog-breaking-changes-template branch August 23, 2024 13:42
@github-actions github-actions bot locked and limited conversation to collaborators Aug 23, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants