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

Allow activesupport 5 or 6 #331

Merged
merged 4 commits into from
Jan 22, 2020
Merged

Allow activesupport 5 or 6 #331

merged 4 commits into from
Jan 22, 2020

Conversation

stevenharman
Copy link
Member

We have a very minimal dependency on active support - limited to the inflection extensions in a generator, and some time extensions in a test. So it seems safe to continue allowing 5, while opening up 6. We'll lock out 7 because it doesn't exist, and we don't know what, if any,
breaking changes it will bring.

We have a very minimal dependency on active support - limited to the
inflection extensions in a generator, and some time extensions in a
test. So it seems safe to continue allowing 5, while opening up 6. We'll
lock out 7 because it doesn't exist, and we don't know what, if any,
breaking changes it will bring.
Rake is way out of date, and we really on use it as a binary, so it's
pretty low risk.

rack-test is purely a dev resource for pliny, even though it's in the
template Gemfile for `pliny new`. But it's got no version restraints
there, so again, very low risk.
@stevenharman stevenharman force-pushed the allow_activesupport_6 branch from 3679ee5 to d05eca5 Compare January 21, 2020 20:32
@stevenharman stevenharman marked this pull request as ready for review January 21, 2020 20:38
Copy link
Contributor

@bensymonds bensymonds left a comment

Choose a reason for hiding this comment

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

This seems ok to me! The only thought I had was whether we want to make travis run the tests against both major versions of activesupport, like it already does with sinatra. It seems pretty straightforward to do so maybe worth it, even given how little activesupport is used..?

@stevenharman
Copy link
Member Author

make travis run the tests against both major versions of activesupport

Excellent idea. I will see get that added.

@stevenharman stevenharman force-pushed the allow_activesupport_6 branch from 092d7b4 to edb859f Compare January 22, 2020 16:55
Because ActiveSupport 6 requires at least Ruby 2.5
@stevenharman stevenharman merged commit 5285883 into master Jan 22, 2020
@stevenharman stevenharman deleted the allow_activesupport_6 branch January 22, 2020 17:13
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.

2 participants