Does not look like this is working with rails 4.

| Dependency Path | Rails Requirement |
+------------------------------------------------+------------------------+
| accept_values_for 0.5.1 | activemodel ~> 3.2.0

Thanks for the cool gem. There are new deprecation Warnings with rspec3.

Deprecation Warnings:
--------------------------------------------------------------------------------
AcceptValuesFor implements a legacy RSpec matcher
protocol. For the current protocol you should expose the failure messages
via the `failure_message` and `failure_message_when_negated` methods.
(Used from /Users/kitsane/src/gsc/spec/models/role_spec.rb:17:in `block (2 levels) in <top (required)>')
--------------------------------------------------------------------------------

It's not always possible or desirable to assign a validation failure to a single attribute, in which case you can add errors for :base. If you do so, however, the validation failure won't satisfy the expectation, because the expectation only looks for errors on the attribute name.

I'm thinking about extending the matcher to compare the number of errors on :base before and after the change. Thoughts?

I see in your gemspec that the version has been bumped to 0.5.0 and there's a Git tag for it as well, but version 0.5.0 of the gem doesn't exist on rubygems.org.

It seems the version from rubygems (0.7.3) matches the version in this repo, but it does not not reflect the new code that supports up to Rails '<5.2'. Any chance you might bump the version and push it up to ruby gems so I can grab the new one via bundler?

thanks

Hi, it seems that you freeze rspec gem version in Gemfile. Is it possible to run accept_values_for using Rspec 3?