Skip to content

Conversation

@brandur
Copy link
Contributor

@brandur brandur commented Dec 25, 2025

Just for fun, upgrade to Ruby 4.0.0 [1] on the day of its release.

[1] https://www.ruby-lang.org/en/news/2025/12/25/ruby-4-0-0-released/

@brandur brandur force-pushed the brandur-ruby-4 branch 3 times, most recently from c01dd78 to d2f4643 Compare December 25, 2025 22:53
Gemfile Outdated
Comment on lines 7 to 8
# gem "ffi", git: "https://github.com/ffi/ffi", branch: "master"
# gem "pg", git: "https://github.com/ged/ruby-pg", branch: "master"
Copy link
Contributor

Choose a reason for hiding this comment

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

don't these need to be uncommented?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Yeah, heh. Didn't end up working. Tried to do this a little too early ... everything's still super broken.

Just for fun, upgrade to Ruby 4.0.0 [1] on the day of its release.

[1] https://www.ruby-lang.org/en/news/2025/12/25/ruby-4-0-0-released/
@brandur
Copy link
Contributor Author

brandur commented Dec 26, 2025

Haha, okay, what a mess. Going to abandon this one for now, but notes to self for later:

  • The pg gem is quite broken, depending on Ruby <= 3.5.
  • The bundled RuboCop can't support Ruby 4.0. Rubocop has a release that supports 4.0, but:
  • Standard is affixed to an old version of RuboCop. Looking at Standard's repo, I couldn't find any evidence that there's a release forthcoming.

Probably the best thing is to just wait a couple weeks/months for all these things to resolve themselves.

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