Skip to content

Conversation

@kotp
Copy link
Member

@kotp kotp commented Dec 13, 2025

  • description in README
  • version for test in CI

@kotp kotp requested a review from a team December 13, 2025 04:49
@kotp
Copy link
Member Author

kotp commented Dec 13, 2025

The impetus was reviewing someone new to Ruby that was using Ruby 2.6 the other day.

@meatball133
Copy link
Member

Would it be possible to update the track to Ruby 3.4? thinking Ruby 4.0 should be released quite soon

@kotp kotp force-pushed the update-ruby-version branch from 8699bea to 3e7f7a8 Compare December 21, 2025 19:11
@kotp
Copy link
Member Author

kotp commented Dec 21, 2025

Would it be possible to update the track to Ruby 3.4? thinking Ruby 4.0 should be released quite soon

https://www.ruby-lang.org/en/downloads/branches/ for reference on EOL schedule.

@meatball133
Copy link
Member

Yes I know that 3.3 is supported for a while longer, but thinking most people likely uses the latest version would it be neat to not be super far behind the latest, thinking breaking changes can be introduced as we can see by the ci failing.

@meatball133
Copy link
Member

But I still think testing 3.3 makes sense, it just that I think all the tooling and the "main" version should be brought to 3.4

@kotp
Copy link
Member Author

kotp commented Jan 7, 2026

But I still think testing 3.3 makes sense, it just that I think all the tooling and the "main" version should be brought to 3.4

We can avoid deprecated and dropped syntax and test for 3.4, knowing that (some) students will be using prior versions, though.

We could update it to 3.3 though, knowing that we have a end of life coming up, and moving it up at that time, though.

I did conscientiously say "want" rather than "need" to indicate the version of 3.4, since it should not be a necessity currently, but an indication that joy will be more likely had with the newer version.

So exercise-tests.yml could be:

ruby-version: [3.3, 3.4]

While leaving the documentation as it is changed here. What do you think?

@kotp kotp force-pushed the update-ruby-version branch from 3e7f7a8 to 7e07e9d Compare January 7, 2026 21:26
@kotp
Copy link
Member Author

kotp commented Jan 7, 2026

The currently failing test is "normal", though undesirable.

@kotp kotp force-pushed the update-ruby-version branch from 7e07e9d to 4f9108e Compare January 7, 2026 21:32
- description in README
- version for test in CI
@kotp kotp force-pushed the update-ruby-version branch from 4f9108e to c13c5f8 Compare January 7, 2026 21:36
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.

3 participants