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

Drop support for EOL'd Ruby versions 2.6 and earlier #1454

Merged
merged 1 commit into from
Jul 12, 2022

Conversation

timrogers
Copy link
Contributor

This drops support for older Ruby versions which have reached end-of-life, so Octokit.rb will only work with Ruby 2.7, 3.0 and 3.1.

Today, the gemspec claims to support v2.0 onwards, but in practice, only v2.3 onwards are tested in CI and actually working.

This drops support for older Ruby versions which have reached
end-of-life, so Octokit.rb will only work with Ruby 2.7, 3.0
and 3.1.

Today, the gemspec claims to support v2.0 onwards, but in
practice, only v2.3 onwards are tested in CI and actually working.
@timrogers timrogers requested a review from nickfloyd July 11, 2022 17:59
@timrogers
Copy link
Contributor Author

@nickfloyd The missing checks are okay as those versions are now dropped from the test matrix 😊

@@ -26,18 +26,8 @@ jobs:
fail-fast: false
matrix:
os: [ ubuntu ]
ruby: [ 2.3, 2.4, 2.5, 2.6, 2.7, '3.0', '3.1', head ]
ruby: [ 2.7, '3.0', '3.1', head ]
faraday: [ '~> 1.0', '~> 2.0' ]
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I am pretty sure we can get rid of the 1.0 reference here... Let me know if that sounds right.

Suggested change
faraday: [ '~> 1.0', '~> 2.0' ]
faraday: '~> 2.0'

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We can still continue to support Faraday 1.x. Dropping support for Faraday 1.x is often pretty painful as there are lots of packages out there that still require it.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Got it... 👍

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I am pretty sure we can get rid of the 1.0 reference here... Let me know if that sounds right.

Suggested change
faraday: [ '~> 1.0', '~> 2.0' ]
faraday: '~> 2.0'

Copy link
Contributor

@nickfloyd nickfloyd left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

❤️

@timrogers timrogers merged commit 27c88aa into main Jul 12, 2022
@nickfloyd nickfloyd deleted the timrogers/ruby-2.7-onwards branch August 10, 2022 16:39
@Mdrajjak334280

This comment was marked as spam.

koic added a commit to koic/octokit.rb that referenced this pull request Feb 14, 2023
Follow up octokit#1454.

gemspec `required_ruby_version` requires 2.7 and higher, so specify
`TargetRubyVersion` to 2.7. Some syntax detected by updating to 2.7 applies.

It also removes `Gemspec/RequiredRubyVersion` cop from .rubocop_todo.yml to
enable the cop so that version mismatch can be detected.
kfcampbell pushed a commit that referenced this pull request Feb 27, 2023
Follow up #1454.

gemspec `required_ruby_version` requires 2.7 and higher, so specify
`TargetRubyVersion` to 2.7. Some syntax detected by updating to 2.7 applies.

It also removes `Gemspec/RequiredRubyVersion` cop from .rubocop_todo.yml to
enable the cop so that version mismatch can be detected.
Copy link

@yehiamitro111 yehiamitro111 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you

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.

4 participants