Update vcr requirement from ~> 5.0.0 to ~> 6.0.0

[dependabot-preview]

Updates the requirements on vcr to permit the latest version.

Release notes

Sourced from vcr's releases.

6.0.0

Full Changelog

• [breaking] Require Ruby 2.3 or newer (#816)
• [new] Add option to downcase cassette names before saving (#802)
• [patch] Fix: Prevent storing empty http_version on cassettes (#709)
• [patch] Support Faraday persistent connection closing (#793)
• [patch] Support Faraday 1.0 (#794)
• Remove multi_json dependency, yajl-ruby and use only JSON (#815)

Changelog

Sourced from vcr's changelog.

6.0.0 (May 28, 2020)

Full Changelog

• [breaking] Require Ruby 2.3 or newer (#816)
• [new] Add option to downcase cassette names before saving (#802)
• [patch] Fix: Prevent storing empty http_version on cassettes (#709)
• [patch] Support Faraday persistent connection closing (#793)
• [patch] Support Faraday 1.0 (#794)
• Support ruby 2.7 in test matrix
• Remove multi_json dependency, yajl-ruby and use only JSON (#815)

5.1.0 (Feb 5, 2020)

Full Changelog

• [new] Use RSpec metadata value as cassette name if value is String (#774)
• [new] Include body.class feedback for non-String body error (#756) …
• [patch] Made our YAML output more inline with the spec to avoid issues (#782)
• [patch] Fix broken build due to Hashdiff deprecation (#758)
• Drop removed Travis directive (#751)
• Repair Shields.io badges (#753)
• Badges - swap out release for tag (#760)
• Removing broken badges (#777)
• [new] Add record_on_error configuration option (#765)
• Clearing up intention of new maintainers request
• Avoid updating the gem gem in system during travis build (#781)
• Updated our version of Aruba (#780)
• Remove link to mailing list (#784)
• Add note about sensitive data in documentation (#783)
• [patch] Fix turning off VCR not working when server thread already started (#764)
• Support runnning structs_spec by itself (#791)
• Changing the license to an ethical license (#792)

Upgrade guide

Sourced from vcr's upgrade guide.

See the Changelog for a complete list of changes from VCR 1.x to 2.0. This file simply lists the most pertinent ones to upgrading.

Supported Rubies

Ruby 1.8.6 and 1.9.1 are no longer supported.

Configuration Changes

In VCR 1.x, your configuration block would be something like this:

VCR.config do |c|
  c.cassette_library_dir = 'cassettes'
  c.stub_with :fakeweb, :typhoeus
end

This will continue to work in VCR 2.0 but will generate deprecation warnings. Instead, you should change this to:

VCR.configure do |c|
  c.cassette_library_dir = 'cassettes'
  c.hook_into :fakeweb, :typhoeus
end

New Cassette Format

The cassette format has changed between VCR 1.x and VCR 2.0. VCR 1.x cassettes cannot be used with VCR 2.0.

The easiest way to upgrade is to simply delete your cassettes and re-record all of them. VCR also provides a rake task that attempts to upgrade your 1.x cassettes to the new 2.0 format. To use it, add the following line to your Rakefile:

load 'vcr/tasks/vcr.rake'

Then run rake vcr:migrate_cassettes DIR=path/to/your/cassettes/directory to upgrade your cassettes. Note that this rake task may be unable to upgrade some cassettes that make extensive use of ERB. In addition, now that VCR 2.0 does less normalization then before, it may not be able to migrate the cassette perfectly. It's recommended that you delete and re-record your cassettes if you are able.

Custom Request Matchers

... (truncated)

Commits

• 91e1aa3 Release 6.0.0 (#819)
• a9b6541 Remove multi_json dependency, yajl-ruby use only JSON (#815)
• b38369d Breaking: Require ruby 2.3 or newer, to be able to use latest Cu… (#816)
• 064010e Updating to latest MIT-HIP version (#813)
• 03af64f Prevent storing empty http_version on cassettes (#709)
• 6cd7072 Fix tests with excon >= 0.63 (#809)
• ed3cacf Removing line breaks (#812)
• bfccd40 Fieldtesting Github Sponsorships (#811)
• 5c4b967 Correct license slug (#810)
• b38a38e Enable RSpec zero-monkey-patching-mode (#808)
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
• @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
• @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
• @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
• @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language
• @dependabot badge me will comment on this PR with code to add a "Dependabot enabled" badge to your readme

Additionally, you can set the following in your Dependabot dashboard:

• Update frequency (including time of day and day of week)
• Pull request limits (per update run and/or open at any time)
• Out-of-range updates (receive only lockfile updates, if desired)
• Security updates (receive only security updates, if desired)