Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Freeze Rails 6.1 support #1223

Open
2 tasks
arielvalentin opened this issue Nov 2, 2024 · 0 comments · May be fixed by #1231
Open
2 tasks

Freeze Rails 6.1 support #1223

arielvalentin opened this issue Nov 2, 2024 · 0 comments · May be fixed by #1231

Comments

@arielvalentin
Copy link
Collaborator

arielvalentin commented Nov 2, 2024

Rails 6.x has reached EoL1.

Security Issues
Minor releases will receive security fixes for two years after the first release in its series. For example, if a theoretical 1.1.0 is released on January 1, 2023, it will receive security fixes until January 1, 2025. After that, it will reach its end-of-life.

List of currently supported releases
7.2.x - Supported until August 9, 2026
7.1.x - Supported until October 1, 2025
7.0.x - Supported until April 1, 2025

  • Remove any Rails 6 specific code and tests
  • Update README to instruct users to pin to a specific gem version

Footnotes

  1. https://rubyonrails.org/2024/10/15/new-maintenance-policy-and-eol-annouments

arielvalentin added a commit to arielvalentin/opentelemetry-ruby-contrib that referenced this issue Nov 5, 2024
This change removes support for Rails 6.1, which has reached EoL.

Users must pin to previous versions of gems and will no longer receive features or bug fixes for instrumentations earlier than this release

Fixes open-telemetry#1223
@arielvalentin arielvalentin linked a pull request Nov 5, 2024 that will close this issue
arielvalentin added a commit to arielvalentin/opentelemetry-ruby-contrib that referenced this issue Nov 24, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant