-
Notifications
You must be signed in to change notification settings - Fork 36
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Bug fix for ruby 2.3.1 #42
base: master
Are you sure you want to change the base?
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the effort! I don't think we should by changing the Rails dependency as part of this though.
Gemfile
Outdated
@@ -1,6 +1,6 @@ | |||
source "http://rubygems.org" | |||
|
|||
gem 'rails', '~> 4.1.0' | |||
gem 'rails', '~> 5.0.1' |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why update this to require Rails 5? I think ideally this should work with both 4 and 5 but seems unrelated to the Ruby 2.3.1 fix anyways?
reportable.gemspec
Outdated
@@ -14,7 +14,7 @@ pkg_files += Dir['spec/**/*.{rb,yml,opts}'] | |||
Gem::Specification.new do |s| | |||
|
|||
s.name = %q{reportable} | |||
s.version = '1.4.2' | |||
s.version = '1.5.0' |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think incrementing the version is unrelated and should be done in a separate PR. Also this would be a patch release as it only fixes a bug and doesn't actually add anything.
No description provided.