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 the broken test matrix and drop old rubies and rails (breaking change) #139

Conversation

jrafanie
Copy link
Member

@jrafanie jrafanie commented Sep 25, 2024

Fix the broken test matrix and drop old rubies and rails

The ci.yaml matrix of rubies and rails versions didn't match the case statement in the Gemfile. Rails 7.0 and 7.1 were not included in the case statement previously.

Now, we sync them up and make the following changes:

Drop:

  • ruby 2.7
  • rails 6.0
  • rails 6.1

Add:

  • ruby 3.3
  • rails 7.2

We set a minimum ruby version of 3.0 and rails 7.0.8 and allow versions less than 8.0, so we can test with 7.1 and 7.2.

Rails 7.1 deprecated and 7.2 removed access to the deprecator instance

See: https://www.github.com/rails/rails/pull/47354

For now, we can maintain support for 7.0-7.2 by manually instantiating the object
and not pass an explicit deprecator.

The ci.yaml matrix of rubies and rails versions didn't match the case statement in the
Gemfile.  Rails 7.0 and 7.1 were not included in the case statement previously.

Now, we sync them up and make the following changes:

Drop:
* ruby 2.7
* rails 6.0
* rails 6.1

Add:
* ruby 3.3
* rails 7.2

We set a minimum ruby version of 3.0 and rails 7.0.8 and allow versions less than
8.0, so we can test with 7.1 and 7.2.
@jrafanie jrafanie added enhancement New feature or request rails7.1 labels Sep 25, 2024
@jrafanie
Copy link
Member Author

ooh, it's failing on rails 7.2 reasons... first one!

See: https://www.github.com/rails/rails/pull/47354

For now, we can maintain support for 7.0-7.2 by manually instantiating the object
and not pass an explicit deprecator.
@jrafanie
Copy link
Member Author

ooh, it's failing on rails 7.2 reasons... first one!

Looks like they removed the automatic access to the singleton instance of the deprecation class. Updated the code and description.

@jrafanie
Copy link
Member Author

I think this is ready to go.

@agrare agrare merged commit 6a0fb54 into ManageIQ:master Sep 29, 2024
12 checks passed
agrare added a commit that referenced this pull request Sep 30, 2024
Changes:
- Drop old versions of ruby and rails, add ruby 3.3 and rails 7.2 (#139)
@jrafanie jrafanie deleted the fix_broken_test_matrix_and_drop_old_rubies_rails branch November 13, 2024 14:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants