Skip to content

Conversation

atesgoral
Copy link
Contributor

Closes #65

Motivation and Context

Streamlining release notes generation when cutting a new release

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)
  • Documentation update

Checklist

  • I have read the MCP Documentation
  • My code follows the repository's style guidelines
  • New and existing tests pass locally
  • I have added appropriate error handling
  • I have added or updated documentation as needed

Additional context

Just told Cursor "Please update the Unreleased section." while the .cursor/rules/release-changelogs.mdc rule is active and CHANGELOG.md is referenced.

@atesgoral atesgoral requested review from topherbullock and koic July 15, 2025 16:14
Copy link
Contributor

@topherbullock topherbullock left a comment

Choose a reason for hiding this comment

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

nice!

@atesgoral atesgoral merged commit e2fe23b into modelcontextprotocol:main Jul 15, 2025
5 checks passed
@atesgoral atesgoral deleted the changelog branch July 15, 2025 19:15
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.

Add CHANGELOG?
2 participants