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

Fix CI, bump minimum Ruby version to 3.1 #41

Merged
merged 7 commits into from
Nov 27, 2024
Merged

Fix CI, bump minimum Ruby version to 3.1 #41

merged 7 commits into from
Nov 27, 2024

Conversation

rosston
Copy link
Member

@rosston rosston commented Nov 15, 2024

CI was breaking on unrelated changes, so let's fix it.

Keeping a version compatible with Ruby 2.7 seems not worth it, given that it's been EOL for over 1.5 years. Ruby 3.0 is also EOL, though only for 6 months. Limiting the versions we support makes testing all this a little easier. So far, we don't need to keep separate Gemfiles for different Ruby versions.

So the biggest change here is dropping support for Ruby 2.7, and adding Ruby 3.2 and 3.3 to CI. That will lead to a version bump to 0.3.0, but I plan to make that change in a separate PR.

@rosston rosston changed the title Empty commit to trigger CI Fix CI Nov 15, 2024
@rosston rosston changed the title Fix CI Fix CI, bump minimum Ruby version to 3.1 Nov 16, 2024
@rosston rosston marked this pull request as ready for review November 16, 2024 00:22
@rosston rosston merged commit cc63f1e into main Nov 27, 2024
3 checks passed
@rosston rosston deleted the fix-ci branch November 27, 2024 16:24
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.

1 participant