Skip to content

Conversation

@maxisbey
Copy link
Contributor

Clarify the branching strategy now that v2 development has begun.

Motivation and Context

With the v2 branching strategy in place (main for v2 development, v1.x for maintenance), the CONTRIBUTING guide needed updating to help contributors target the correct branch.

How Has This Been Tested?

Documentation change only.

Breaking Changes

None.

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

Clarify that main is now the v2 development branch where breaking
changes are welcome, and v1.x is the maintenance branch for security
and critical bug fixes only.
@maxisbey maxisbey merged commit 3f6b059 into main Dec 19, 2025
21 checks passed
@maxisbey maxisbey deleted the docs/update-contributing-branching-strategy branch December 19, 2025 18:11
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.

3 participants