We have a problem with Ruby 3.3.0-rc1 and Rails 7.0: https://github.com/thoughtbot/shoulda-matchers/actions/runs/7282196165/job/19844139180?pr=1588

Error: Your Ruby version is 3.3.0.rc1, but your Gemfile specified 3.3.0.

I also opened a issue on Rails: rails/rails#50413

I'm continuing to work on it.

The problem reported on my previous comment was fixed on Rails 7.1, but it won't be back port because it's in fact a feature.

For the time being, let's exclude the case where Rails is version 7.0.x and Ruby 3.3.0.rc-1.

After merging this PR, let's focus on our next release.

There is two more PRs for it.

One updating the CHANGELOG and other updating the Version.
Examples:

• [skip ci] Bring CHANGELOG up to date #1517
• Bump version to 5.3.0 #1531

I'm going to work on the Changelog ASAP.

What do you think about working on the other PR, @matsales28? Have you read this(https://github.com/thoughtbot/shoulda-matchers/blob/main/MAINTAINING.md#issuing-a-new-release)?

I recommend making the next release a major one, given that we have discontinued support for certain Ruby and Rails versions.

What do you think about working on the other PR, @matsales28? Have you read this(https://github.com/thoughtbot/shoulda-matchers/blob/main/MAINTAINING.md#issuing-a-new-release)?

I recommend making the next release a major one, given that we have discontinued support for certain Ruby and Rails versions.

Yes! I've set up the ruby gems access for me. I can make the version PR and publish it to ruby gems, no problem!