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

Remove Rails 5.1 support #3328

Merged
merged 2 commits into from
Jan 15, 2020

Conversation

kennyadsl
Copy link
Member

@kennyadsl kennyadsl commented Sep 4, 2019

Description
Our code is still compatible with Rails 5.1 but that version is in its EOL phase, so it's not receiving security patches anymore.

This PR removes support for Rails 5.1, and it's a follow-up of #3333. We should merge this PR after we release the next version, probably 2.10.

Checklist:

  • I have followed Pull Request guidelines
  • I have added a detailed description into each commit message
  • [ ] I have updated Guides and README accordingly to this change (if needed)
  • [ ] I have added tests to cover this change (if needed)

Copy link
Contributor

@jacobherrington jacobherrington left a comment

Choose a reason for hiding this comment

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

I think I am OK with dropping support for Rails 5.1 now that it is EOL.

Copy link
Member

@tvdeyen tvdeyen left a comment

Choose a reason for hiding this comment

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

Are we talking about Rails 5.0 or 5.1? Since 5.1 has not reached end of live according to https://guides.rubyonrails.org/maintenance_policy.html

5.1 is still receiving security patches and 5.0 even severe security patches.

Am I missing something?

@kennyadsl
Copy link
Member Author

@tvdeyen I think that document is outdated, according to https://rubyonrails.org/security/

@kennyadsl
Copy link
Member Author

Copy link
Member

@tvdeyen tvdeyen left a comment

Choose a reason for hiding this comment

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

I see. Thanks for pointing me to the correct file 👌

Still, I am hesitant with removing this now. We should at least wait another minor version. I don’t want our users to run into situations where they want to update Solidus for a bug fix or new feature and also force them to upgrade Rails.

Mayor dependency changes like that should always be done separate from bug fixes or mayor new features.

Other than that I am fine with removing it.

@kennyadsl
Copy link
Member Author

@tvdeyen what about printing a deprecation warning if Rails 5.1 is used and just remove it from the CI?

@tvdeyen
Copy link
Member

tvdeyen commented Sep 13, 2019

This sounds like a good idea.

@kennyadsl kennyadsl mentioned this pull request Sep 13, 2019
2 tasks
@kennyadsl kennyadsl force-pushed the kennyadsl/remove-rails-5-1 branch from 7ce33e2 to 2a8cde5 Compare September 13, 2019 11:54
@kennyadsl
Copy link
Member Author

I've created #3333 and updated this PR, so it's ready to merge after the next release.

@kennyadsl kennyadsl force-pushed the kennyadsl/remove-rails-5-1 branch from 2a8cde5 to d21f025 Compare January 15, 2020 15:21
@kennyadsl kennyadsl merged commit 958f29e into solidusio:master Jan 15, 2020
@kennyadsl kennyadsl deleted the kennyadsl/remove-rails-5-1 branch January 15, 2020 16:59
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.

4 participants