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

Deprecate Rails 5.1 #3333

Merged
merged 3 commits into from
Oct 3, 2019

Conversation

kennyadsl
Copy link
Member

Description
This PR removes Rails 5.1 from our CI and prints a warning message in the Rails console for users who are still using Rails 5.1.

After the next version release (2.10?), we can merge #3328 and complete this transition.

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)

Rails 5.1 will not be suported from Solidus starting from the next
version. It is in its EOL phase and will not receive security patches
anymore.
No need to run tests against Rails 5.1, it's deprecated.
It was already obsolete starting with Rails 5.1.
@kennyadsl kennyadsl self-assigned this Sep 13, 2019
@kennyadsl kennyadsl mentioned this pull request Sep 13, 2019
2 tasks
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.

Nicely done 👏

Read more on upgrading from Rails 5.1 to Rails 5.2 here:
https://guides.rubyonrails.org/upgrading_ruby_on_rails.html#upgrading-from-rails-5-1-to-rails-5-2

HEREDOC
Copy link
Member

Choose a reason for hiding this comment

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

Nice!

Copy link
Member

@spaghetticode spaghetticode left a comment

Choose a reason for hiding this comment

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

@kennyadsl 👍 thank you!

@kennyadsl
Copy link
Member Author

I've one doubt here: if we remove testing against Rails 5.1 in the CI, we'll never notice if we are introducing breaking changes for Rails 5.1. Not sure I still want to remove it, we'll talk in the next core team meeting maybe?

@kennyadsl
Copy link
Member Author

Merging without 5.1 tests to be run. They have been removed from CircleCI with this same PR.

@kennyadsl kennyadsl merged commit 74f43ca into solidusio:master Oct 3, 2019
@kennyadsl kennyadsl deleted the kennyasdl/deprecate-rails-5-1 branch March 5, 2021 20:15
waiting-for-dev added a commit to nebulab/solidus that referenced this pull request Jun 23, 2022
Rails 5.2 reached EOL on June 1st, 2022 [1]. We're going to deprecate it
on Solidus v3.2, and remove support on the next major.

- We warn when we detect that version is used.
- We remove the Rails 5.2 job in the CI.
- We remove branching on Rails 5.2 in the specs.

We've taken solidusio#3333 for inspiration.

- [1] - https://guides.rubyonrails.org/maintenance_policy.html
waiting-for-dev added a commit to nebulab/solidus that referenced this pull request Jun 23, 2022
Rails 5.2 reached EOL on June 1st, 2022 [1]. We're going to deprecate it
on Solidus v3.2, and remove support on the next major.

- We warn when we detect that version is used.
- We remove the Rails 5.2 job in the CI.
- We remove branching on Rails 5.2 in the specs.

We've taken solidusio#3333 for inspiration.

- [1] - https://guides.rubyonrails.org/maintenance_policy.html
waiting-for-dev added a commit to nebulab/solidus that referenced this pull request Jun 24, 2022
Rails 5.2 reached EOL on June 1st, 2022 [1]. We're going to deprecate it
on Solidus v3.2, and remove support on the next major.

- We warn when we detect that version is used.
- We remove the Rails 5.2 job in the CI.
- We remove branching on Rails 5.2 in the specs.

We've taken solidusio#3333 for inspiration.

- [1] - https://guides.rubyonrails.org/maintenance_policy.html
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