Ruby 3.2 EOL 2026-03-31

[arielvalentin]

https://www.ruby-lang.org/en/downloads/branches/#ruby-32

Drop compatibility testing
Update minimal Ruby version in gemspec
Document last supported version of contrib packages

[YousefHadder]

Hi 👋 I'd like to pick this up. I've audited both repos and have a plan ready — sharing it here for visibility and to get answers on a couple of open questions before opening PRs.

Plan

This requires changes in two repos — both PRs can land in parallel since there's no hard dependency between them.

PR 1: opentelemetry-ruby (core) — feat!: drop support for EOL Ruby 3.1 and 3.2

The core repo's minimum is still >= 3.1 (it was never bumped when 3.1 went EOL last March), so this PR drops both 3.1 and 3.2 in one go. ~23 files, all mechanical:

• 20 gemspecs: '>= 3.1' → '>= 3.3'
• .github/workflows/ci.yml: Remove the Ruby 3.2 and 3.1 test steps from all 3 jobs (base, exporters, propagators); move yard/rubocop/build flags to the 3.3 step
• contrib/rubocop.yml: TargetRubyVersion: "3.1" → "3.3"
• .github/ISSUE_TEMPLATE/bug_report.md: Update example Ruby version

The Jaeger exporter (< 3.2) is left untouched — see open question below.

PR 2: opentelemetry-ruby-contrib — feat!: drop support for EOL Ruby 3.2

The contrib repo already dropped 3.1 in #1701, so this just bumps 3.2 → 3.3. ~72 files:

• 64 gemspecs: via bin/update-ruby-version 3.3
• 6 CI workflow files: Remove Ruby 3.2 test steps, move quality gate flags (yard, rubocop, coverage, build) to the 3.3 step
• .rubocop.yml: TargetRubyVersion: 3.2 → 3.3
• README.md: Update supported version docs and add 3.2 EOL note (following the existing 3.1 pattern)
• Code audit: Check for any RUBY_VERSION guards or Appraisals conditions that reference 3.2

No Ruby-version-conditional code paths were found in either repo during the audit.

Open Questions

1. Jaeger exporter in opentelemetry-ruby — The core repo still has exporter/jaeger pinned to required_ruby_version = '< 3.2' due to the thrift gem incompatibility. Jaeger itself is deprecated in the OTel ecosystem. Should we remove the Jaeger exporter entirely as part of this effort, or leave it as-is and handle separately?

2. Should there be a matching tracking issue in opentelemetry-ruby? — This issue tracks contrib, but the core repo also needs the same treatment (it's still on >= 3.1). Happy to open one if that's preferred.

3. Anything else to include? — The bin/update-ruby-version script in contrib and the CONTRIBUTING.md checklist are great — I'll follow both. Is there anything else I should be aware of (e.g., required checks in repo settings that need updating after the CI changes)?

Happy to open the PRs once we're aligned on the approach.

[arielvalentin]

@YousefHadder thanks for your help!

Should there be a matching tracking issue in opentelemetry-ruby? — This issue tracks contrib, but the core repo also needs the same treatment (it's still on >= 3.1). Happy to open one if that's preferred.

Yes please.

.rubocop.yml: TargetRubyVersion: 3.2 → 3.3

Updating Rubocop target version will be ok if there are few changes required. If there are significant changes I would like to review those changes separately.

[YousefHadder]

@arielvalentin Thanks for the feedback, I would love to hear from you about the Jaeger exporter open question.

[arielvalentin]

@YousefHadder the Jaeger exporter is no longer supported and has been deprecated https://github.com/open-telemetry/opentelemetry-ruby/tree/main/exporter/jaeger#warning-eol-notice-2025-12-31

There no need to update it.