Skip to content

Conversation

@koic
Copy link
Member

@koic koic commented May 23, 2025

Motivation and Context

RubyGems may be used across a wide range of Ruby versions, from the minimum supported version to development versions.

To allow local development with any Ruby version,
the Ruby version is not locked using a .ruby-version file.

This enables developers to work with their preferred Ruby version and frees repository maintainers from the need to update .ruby-version.

Additionally, because testing against supported Ruby versions is performed in CI before release, the version in .ruby-version is not important.

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

RubyGems may be used across a wide range of Ruby versions,
from the minimum supported version to development versions.

To allow local development with any Ruby version,
the Ruby version is not locked using a `.ruby-version` file.

This enables developers to work with their preferred Ruby version and
frees repository maintainers from the need to update `.ruby-version`.

Additionally, because testing against supported Ruby versions is performed
in CI before release, the version in `.ruby-version` is not important.
@atesgoral atesgoral merged commit 89ef9d8 into modelcontextprotocol:main May 24, 2025
4 checks passed
@koic koic deleted the remove_dot_ruby_version branch May 24, 2025 04:53
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.

2 participants