(maint) Constrain orchestrator_client to < 0.7.1 #528
+31
−23
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.
Summary
Based on puppetlabs/puppetlabs-puppet_agent#743 to fix an issue with the version 0.7.1 of orchestrator_client
"The 0.7.1 release of orchestrator_client broadened its dependency on Faraday (see puppetlabs/orchestrator_client-ruby@6f8661e). This change has caused Bundler to resolve Faraday in unexpected ways when there are other Gems with dependencies on Faraday.
This commit constrains orchestrator_client to < 0.7.1 until this issue is resolved."
Additional Context
Add any additional context about the problem here.
Related Issues (if any)
rubygems/rubygems#8286
Checklist
Changes include test coverage?
Have you updated the documentation?