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

Support Ruby 2.4.0 #389

Merged
merged 5 commits into from Jan 6, 2017
Merged

Support Ruby 2.4.0 #389

merged 5 commits into from Jan 6, 2017

Conversation

camelmasa
Copy link
Contributor

I'd like to use this gem with Ruby 2.4.0.
I couldn't bundle install using Ruby 2.4.0 because activesupport 4.x is depending old json gem.

@dblock
Copy link
Member

dblock commented Jan 5, 2017

If you can get the build to be green we could take it. Add ruby 2.4.0 to the build matrix.

@camelmasa
Copy link
Contributor Author

@dblock Thanks for response. I'll fix that tomorrow 👍

@michaelherold
Copy link
Member

I think we might need to start using appraisals, since we support environments with Rails versions < 5. Rails 5 requires Ruby 2.2+ so it breaks our test environment for versions less than that.

@dblock
Copy link
Member

dblock commented Jan 5, 2017

Or you can do some if's in the Gemfile, too.

@camelmasa camelmasa force-pushed the bump-as branch 3 times, most recently from e2ccf3f to 8216e95 Compare January 5, 2017 23:19
@camelmasa
Copy link
Contributor Author

camelmasa commented Jan 5, 2017

@michaelherold @dblock Thank you for suggestions. I updated a commit. That was passed tests.

I'll create other PR for adding ruby 2.4.0 to .travis.yml after merged this PR and then I'll fix deprecation warnings for Fixnum and Bignum.

I'll continue to add commits on this PR.

  • Add ruby 2.4.0 to .travis.yml
  • Fix deprecation warnings for Fixnum and Bignum

@camelmasa camelmasa changed the title Bump activesupport gem to 5.x on test environment Support Ruby 2.4.0 Jan 6, 2017
@camelmasa
Copy link
Contributor Author

I added commits and updated CHANGELOG. @dblock Could you review when you have time ❓

@dblock
Copy link
Member

dblock commented Jan 6, 2017

Looks good to me, merging.

@dblock dblock merged commit 87582b5 into hashie:master Jan 6, 2017
@camelmasa
Copy link
Contributor Author

@dblock Thanks !

@camelmasa camelmasa deleted the bump-as branch January 6, 2017 12:50
@lsdr
Copy link

lsdr commented Jan 30, 2017

I'd like to use hashie with Ruby 2.4 too. Do you guys have an idea when I'll release the next version?

@michaelherold
Copy link
Member

I don't think there's anything holding that up. I can work on getting a release out tomorrow unless @dblock knows of some reason we should hold off.

@lsdr
Copy link

lsdr commented Jan 30, 2017

@michaelherold that would be great, thanks! And if there's anything I can do to help, I'm willing to.

@dblock
Copy link
Member

dblock commented Jan 31, 2017

I hereby issue an executive order to release the next version of Hashie!

😢

@dblock
Copy link
Member

dblock commented Jan 31, 2017

More seriously, thanks so much for your help @michaelherold!

@michaelherold
Copy link
Member

Hmm 🤔

We have a change that is listed in the upgrading document that is technically a breaking change.

It feels more like a bug fix to me than a change of contract. Thus, I don't think we need a major version bump.

I do think we need a minor version bump to 3.5.0 since we have the added functionality of Hashie::Logger in this release. Do you agree?

@dblock
Copy link
Member

dblock commented Jan 31, 2017

I agree.

@michaelherold
Copy link
Member

Done, thanks for the kick in the pants, @lsdr!

@lsdr
Copy link

lsdr commented Jan 31, 2017

Awesome! Thank you @michaelherold and @dblock!

jsonn pushed a commit to jsonn/pkgsrc that referenced this pull request Mar 20, 2017
# Change Log

## [3.5.5] - 2017-02-24

[3.5.5]: hashie/hashie@v3.5.4...v3.5.5

### Added

* [#326](hashie/hashie#326): Added `Hashie::Extensions::Mash::KeepOriginalKeys` to give Mashes the ability to keep the original structure given to it - [@michaelherold](https://github.com/michaelherold).

### Fixed

* [#415](hashie/hashie#415): Fixed Mash logging keys multiple times which lead to a bad user experience or, in some cases, errors - [@michaelherold](https://github.com/michaelherold).

## [3.5.4] - 2017-02-22

[3.5.4]: hashie/hashie@v3.5.3...v3.5.4

### Added

* [#412](hashie/hashie#412): Added a Hashie::Extensions::Mash::SymbolizeKeys extension that overrides the default stringification behavior for keys - [@michaelherold](https://github.com/michaelherold).

### Fixed

* [#409](hashie/hashie#409): Fixed Railtie detection for projects where Rails is defined but Railties are not availble - [@CallumD](https://github.com/callumd).
* [#411](hashie/hashie#411): Fixed a performance regression from 3.4.3 that caused a 10x slowdown in OmniAuth - [@michaelherold](https://github.com/michaelherold).

## [3.5.3] - 2017-02-11

[3.5.3]: hashie/hashie@v3.5.2...v3.5.3

### Fixed

* [#402](hashie/hashie#402): Use a Railtie to set Hashie.logger on rails boot - [@matthewrudy](https://github.com/matthewrudy).
* [#406](hashie/hashie#406): Ensure that subclasses that disable warnings propagate that setting to grandchild classes - [@michaelherold](https://github.com/michaelherold).
* Your contribution here.

## [3.5.2] - 2017-02-10

[3.5.2]: hashie/hashie@v3.5.1...v3.5.2

### Added

* [#395](hashie/hashie#395): Add the ability to disable warnings in Mash subclasses - [@michaelherold](https://github.com/michaelherold).
* [#400](hashie/hashie#400): Fix Hashie.logger load and set the Hashie logger to the Rails logger in a Rails environment - [@michaelherold](https://github.com/michaelherold).

### Fixed

* [#396](hashie/hashie#396): Fix for specs in #381: Incorrect use of shared context meant example was not being run - [@biinari](https://github.com/biinari).
* [#399](hashie/hashie#399): Fix passing Pathname object to Hashie::Mesh.load() - [@albb0920](https://github.com/albb0920).

### Miscellanous

* [#397](hashie/hashie#397): Add the integration specs harness into the main test tasks - [@michaelherold](https://github.com/michaelherold).

## [3.5.1] - 2017-01-31

* [#392](hashie/hashie#392): Fix for #391: Require all dependencies of Hashie::Mash - [@dblock](https://github.com/dblock).

[3.5.1]: hashie/hashie@v3.5.0...v3.5.1

## [3.5.0] - 2017-01-31

* [#386](hashie/hashie#386): Fix for #385: Make `deep_merge` always `deep_dup` nested hashes before merging them in so that there are no shared references between the two hashes being merged. - [@mltsy](https://github.com/mltsy).
* [#389](hashie/hashie#389): Support Ruby 2.4.0 - [@camelmasa](https://github.com/camelmasa).

[3.5.0]: hashie/hashie@v3.4.6...v3.5.0

### Added

* [#381](hashie/hashie#381): Add a logging layer that lets us report potential issues to our users. As the first logged issue, report when a `Hashie::Mash` is attempting to overwrite a built-in method, since that is one of our number one questions - [@michaelherold](https://github.com/michaelherold).

### Changed

* [#384](hashie/hashie#384): Updated to CodeClimate 1.x - [@boffbowsh](https://github.com/boffbowsh).

### Fixed

* [#369](hashie/hashie#369): If a translation for a property exists when using IndifferentAccess and IgnoreUndeclared, use the translation to find the property - [@whitethunder](https://github.com/whitethunder).
* [#376](hashie/hashie#376): Leave string index unchanged if it can't be converted to integer for Array#dig - [@sazor](https://github.com/sazor).
* [#377](hashie/hashie#377): Dont use Rubygems to check ruby version - [@sazor](https://github.com/sazor).
* [#378](hashie/hashie#378): Deep find all searches inside all nested hashes - [@sazor](https://github.com/sazor).
* [#380](hashie/hashie#380): Evaluate procs default values of Dash in object initialization - [@sazor](https://github.com/sazor).

### Miscellanous

* [#387](hashie/hashie#387): Fix builds failing due to Rake 11 having a breaking change - [@michaelherold](https://github.com/michaelherold).
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.

None yet

4 participants