-
-
Notifications
You must be signed in to change notification settings - Fork 264
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
Relax rack dependency for Rails 4 #68
Conversation
I think your suggestion is a good one. Probably we should also leave some note in the gemspec about that dependency. |
0e96c23
to
bd166f6
Compare
Would it be possible to have a rubocop-rails build 2.0.1 including this change? All previous rubocop-rails versions have been yanked from rubygems. Now all our rails 4 project builds are broken due to rubocop-rails not being available anymore. |
RuboCop Rails 2.0.1 has been released. This release includes this patch. |
This PR drops development dependency on Rack gem. This dependency was introduced at rubocop#5597 for `Rails/HttpStatus` cop. Rails cops has been removed in rubocop#7095 from RuboCop core and the dependency on Rack gem is maintained by RuboCop Rails repo. rubocop/rubocop-rails#68
This PR drops development dependency on Rack gem. This dependency was introduced at #5597 for `Rails/HttpStatus` cop. Rails cops has been removed in #7095 from RuboCop core and the dependency on Rack gem is maintained by RuboCop Rails repo. rubocop/rubocop-rails#68
This PR drops Rails 3 support. RuboCop core was supported Rails 4+. https://github.com/rubocop-hq/rubocop/tree/v0.71.0#compatibility > The Rails cops support the following versions: > > - Rails 4.0+ It conforms to the expected behavior of RuboCop core originally. And Rails is maintained at 4.2.Z or higher. > 4 Severe Security Issues > For severe security issues all releases in the current major series, and > also the last major release series will receive patches and new > versions. The classification of the security issue is judged by the core > team. > > Currently included series: 5.2.Z, 5.1.Z, 5.0.Z, 4.2.Z. https://guides.rubyonrails.org/maintenance_policy.html The following is the RuboCop Rails and Rails 4 use case. rubocop#68
This PR drops Rails 3 support. RuboCop core was supported Rails 4+. https://github.com/rubocop-hq/rubocop/tree/v0.71.0#compatibility > The Rails cops support the following versions: > > - Rails 4.0+ It conforms to the expected behavior of RuboCop core originally. And Rails is maintained at 4.2.Z or higher. > 4 Severe Security Issues > For severe security issues all releases in the current major series, and > also the last major release series will receive patches and new > versions. The classification of the security issue is judged by the core > team. > > Currently included series: 5.2.Z, 5.1.Z, 5.0.Z, 4.2.Z. https://guides.rubyonrails.org/maintenance_policy.html The following is the RuboCop Rails and Rails 4 use case. rubocop#68
This is related to #37.
rack
was recently made a runtime dependency: #36:Now this conflicts with an older Rails 4 app of ours which requires an older rack version:
The only rack interface that is used seems to be
::Rack::Utils::SYMBOL_TO_STATUS_CODE
which first appeared in rack 1.1: rack/rack@5c4bd17Is there a particular reason why you enforce rack >= 2.0 or could we relax that dependency?