Pin rspec-expectations due to private API change #6
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
In this change, we are introducing a temporary version pin of the rspec-expectations gem to version v3.12.3.
As part of the v3.12.4/v3.13.0 releases, the private API class RSpec::Matchers::ExpectedsForMultipleDiffs was renamed to RSpec::Matchers::MultiMatcherDiff 1. chefspec does make use of this class in one instance.
A future change should be introduced to properly address this class dependency. Possible options include replicating a minimal replacement, or porting the class to equivalent custom matcher with the chefspec codebase.
Related Issue
Here is an example of a spec failing within a CD/CI pipeline that automatically pulls in the latest version of the chefspec gem. Note, that chefspec did not have a new release, but the permissive version matching against rspec now introduces this runtime error.
Types of changes
Checklist:
Gemfile.lock
has changed, I have used--conservative
to do it and included the full output in the Description above.