Summary

Use 10.0.0 as the deliberate release to remove support for end-of-life Ruby versions instead of letting that happen implicitly through dependency updates.

Why

• Ruby 2.7 and 3.0 are already end-of-life.
• The current 9.x line still carries CI and compatibility expectations for those older Rubies.
• Bundler and RubyGems upgrades increasingly raise the minimum supported Ruby, so future updates should land behind an explicit major-version boundary.

Proposed scope for 10.0.0

• Decide and document the new minimum supported Ruby version.
• Remove unsupported Ruby versions from CI.
• Revisit the supported Rails matrix and drop unsupported upstream Rails series where appropriate.
• Update required_ruby_version, docs, changelog, and release notes together.
• Make any Bundler/RubyGems baseline changes part of the same explicit release plan.

Notes

This issue is meant to track the policy change and release planning, not to force that change into the current 9.x branch through incidental lockfile updates.