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

Update ruby rails dependencies (breaking change) #50

Merged
merged 2 commits into from
Sep 24, 2024

Conversation

jrafanie
Copy link
Member

@jrafanie jrafanie commented Sep 24, 2024

Use core minimum but allow 7.0/7.1/7.2 since core sets upper limit

Drop end of life rubies and rails and add new versions

Ensure we're testing and supporting community supported
versions.

Drop:

  • ruby 2.7
  • rails 6.0
  • rails 6.1

Add:

  • ruby 3.2
  • ruby 3.3
  • rails 7.1
  • rails 7.2

Note: ruby 3.0 is not difficult to keep maintaining for now but it's on the chopping block.

This should be safe to use as is since the core application sets the rails version.
This will allow us to test with other versions on master.
Gemfile Outdated
"~>7.2.1"
when "7.1"
"~>7.1.4"
else "7.0"
Copy link
Member

Choose a reason for hiding this comment

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

Is this valid syntax?

Copy link
Member

Choose a reason for hiding this comment

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

I think this will actually created a combined string like "7.0~>7.0.8" cause it will see two strings side by side.

Copy link
Member Author

Choose a reason for hiding this comment

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

Interesting, it's a bug but I think it does the right thing. Let me fix it.

Copy link
Member Author

Choose a reason for hiding this comment

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

That was a wild goose chase... but I'll fix this and test with ruby 3.0-3.3 and rails 7.0-7.2.

Copy link
Member Author

Choose a reason for hiding this comment

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

done... checking ci results...

Copy link
Member Author

Choose a reason for hiding this comment

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

It's all good now. 😅

@@ -12,13 +12,13 @@ jobs:
strategy:
matrix:
ruby-version:
- '2.7'
- '3.0'
Copy link
Member

Choose a reason for hiding this comment

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

I thought our app still supported 3.0?

Copy link
Member Author

Choose a reason for hiding this comment

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

3.0 is end of life but I can keep it around. I guess the same can be said about rails 6.1.

Copy link
Member Author

Choose a reason for hiding this comment

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

ok, fixed

Ensure we're testing and supporting community supported
versions.

Drop:
* ruby 2.7
* rails 6.0
* rails 6.1

Add:
* ruby 3.2
* ruby 3.3
* rails 7.1
* rails 7.2

Note: ruby 3.0 is not difficult to keep maintaining for now but it's on the chopping block.
@jrafanie jrafanie force-pushed the update_ruby_rails_dependencies branch from 5d019bf to a82cd58 Compare September 24, 2024 18:37
@Fryguy Fryguy merged commit 29165c8 into ManageIQ:master Sep 24, 2024
12 checks passed
@jrafanie jrafanie deleted the update_ruby_rails_dependencies branch September 26, 2024 18:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants