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

Support for ruby 3.2. Drop older ruby versions and que #33

Open
wants to merge 16 commits into
base: master
Choose a base branch
from

Conversation

apuratepp
Copy link
Member

@apuratepp apuratepp commented Sep 28, 2023

Added

  • Support ruby 3.2
  • Support rails 7
  • Support ruby-kafka 1.5
  • Support sidekiq 6.0

Removed

  • Drop support for ruby < 3.2
  • Drop support for que
  • Drop support for sinatra 1.4

@apuratepp apuratepp added the wip label Sep 28, 2023
@apuratepp apuratepp changed the title Drop support for ruby < 3.2 Support for ruby 3.2. Drop older ruby versions and que Sep 29, 2023
Comment on lines -25 to -31
- gemfiles/que_0.12.2.gemfile
- gemfiles/que_0.12.3.gemfile
- gemfiles/rails_5.2.gemfile
- gemfiles/shoryuken_4.0.gemfile
- gemfiles/sidekiq_4.2.gemfile
- gemfiles/sinatra_1.4.gemfile
- gemfiles/sinatra_2.0.gemfile

Choose a reason for hiding this comment

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

Did all of those fail? If not, id say we leave the most reasonable ones still active!? That way we can ensure that some older versions are still running without major issues.

@@ -19,22 +19,19 @@ jobs:
runs-on: ubuntu-latest
strategy:
matrix:
ruby: ['2.5.1', '2.7.2', '2.6.5']
ruby: ['3.2.2']

Choose a reason for hiding this comment

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

Why 3.2? At least ruby 3.0.x is still in security maintenance phase https://www.ruby-lang.org/en/downloads/ so id say its better to have the active ruby versions supported!?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants