diff options
| author | Lamont Granquist <lamont@scriptkiddie.org> | 2018-09-25 22:33:30 -0700 |
|---|---|---|
| committer | Lamont Granquist <lamont@scriptkiddie.org> | 2018-09-25 22:33:30 -0700 |
| commit | 9fb62cda391591e0369ce32b8c8ec1afd3dfb8af (patch) | |
| tree | ddfda448b6b63e88da8ed2e865a29311c18538bf /chef.gemspec | |
| parent | 671a1a740209a021fd31f451ec233bd884a5a37f (diff) | |
| download | chef-9fb62cda391591e0369ce32b8c8ec1afd3dfb8af.tar.gz | |
Work around rspec 3.8.0 issues
Problem is described in detail here:
https://github.com/rspec/rspec-expectations/issues/1068#issuecomment-424580564
Note that this is self-inflicted damage and our pattern of having #to_hash
on objects be called by #to_json and to produce a serialized 'flavor' of
the object breaks what ruby's semantics are supposed to be and those
should all be `#to_h` methods, and we should deprecate `#to_hash` but I
imagine that will be a reasonably large breaking change (Although
hopefully most of the use by users will be Node#to_hash which is
entirely correct usage since that thing is actually a kind of glorified
Hash-like monster).
Signed-off-by: Lamont Granquist <lamont@scriptkiddie.org>
Diffstat (limited to 'chef.gemspec')
| -rw-r--r-- | chef.gemspec | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/chef.gemspec b/chef.gemspec index 6cbbe4b7fc..6ad2e4e2c3 100644 --- a/chef.gemspec +++ b/chef.gemspec @@ -41,7 +41,7 @@ Gem::Specification.new do |s| s.add_dependency "iso8601", "~> 0.11.0" # Audit mode requires these, so they are non-developmental dependencies now - %w{rspec-core rspec-expectations rspec-mocks}.each { |gem| s.add_dependency gem, "~> 3.5", "< 3.8" } + %w{rspec-core rspec-expectations rspec-mocks}.each { |gem| s.add_dependency gem, "~> 3.5" } s.add_dependency "rspec_junit_formatter", "~> 0.2.0" s.add_dependency "serverspec", "~> 2.7" s.add_dependency "specinfra", "~> 2.10" |