Skip to content

Relax rails dependency constraint to support the 4.2.x releases. #1318

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

Merged
merged 1 commit into from
Feb 21, 2015
Merged

Relax rails dependency constraint to support the 4.2.x releases. #1318

merged 1 commit into from
Feb 21, 2015

Conversation

lucasmazza
Copy link
Contributor

The previous constraint would only go as up as 4.2.0, thus making rspec-rails
incompatible with any of the patch releases of the rails 4.2.x series.

The previous constraint would only go as up as `4.2.0`, thus making `rspec-rails`
incompatible with any of the patch releases of the rails 4.2.x series.
@lucasmazza
Copy link
Contributor Author

This change is required to use rspec-rails with the 4.2.1 rc released today (http://weblog.rubyonrails.org/2015/2/20/Rails-4-2-1-rc1-and-4-1-10-rc1-have-been-released/), would be awesome to have a new release of the 3.2.x series of rspec-rails.

@cupakromer
Copy link
Member

❤️ Thanks!!!

cupakromer added a commit that referenced this pull request Feb 21, 2015
Relax `rails` dependency constraint to support the `4.2.x` releases.
@cupakromer cupakromer merged commit b541ac2 into rspec:master Feb 21, 2015
cupakromer added a commit that referenced this pull request Feb 21, 2015
cupakromer added a commit that referenced this pull request Feb 21, 2015
cupakromer added a commit that referenced this pull request Feb 21, 2015
@lucasmazza lucasmazza deleted the lm-rails-4-2-1 branch February 21, 2015 17:50
@lucasmazza
Copy link
Contributor Author

@cupakromer thanks for the merge! Any plans on releasing a new version (either something like 3.2.1 or the 3.3.x) with this?

@cupakromer
Copy link
Member

@lucasmazza yes, we plan on getting a 3.2.1 patch release out in the next day or two.

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