Skip to content

Conversation

@jbourassa
Copy link
Collaborator

@jbourassa jbourassa commented Dec 26, 2025

  • Skip locking fronzen strings
  • Adapt Ractor spec for Ruby 4.0 -- the Ractor API changed
  • Used Ruby 4.0 for all workflows

TODOs:

  • Figure out how to get ci-data to inect Ruby 4.0 into the test matrix.

Locking a frozen string now raises an exception:
https://bugs.ruby-lang.org/issues/20998

Locking should not be necessary: we know for a fact a frozen string
can't be modified, so let's just not lock.
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.

2 participants