Update puppet_forge requirement from >= 2.3.0, < 4.0.0 to >= 2.3.0, < 6.0.0

[dependabot[bot]]

Updates the requirements on puppet_forge to permit the latest version.

Changelog

Sourced from puppet_forge's changelog.

v2.3.4 - 2020-03-31

• Update the forge API url to forgeapi.puppet.com (instead of using the older puppetlabs.com domain).
• Allow versions of the faraday_middleware dependency up to 0.15.

v2.3.3 - 2020-02-20

Changed

• Allow versions of faraday up to 0.18

v2.3.2 - 2020-02-05

Fixed

• Catch and handle the new Faraday::TimeoutErrors which are occasionally surfaced by the the typheous adapter with more recent verions of libcurl, and log them the same way that Faraday::ConnectionFailed errors are already logged.

Changed

• Allow for using faraday_middleware versions in the 0.13.x series.

v2.3.1 - 2019-11-15

Fixed

• Fixed an issue where proxy configurations were being ignored by expanding the range of acceptable versions of the faraday gem dependency and specifically excluding the version that was ignoring proxy configuration options.

v2.3.0 - 2019-07-09

Changed

• Updated PuppetForge::V3::Release#verify method to use file_sha256 checksum from Forge API when available.
• Added an allow_md5 param to PuppetForge::V3::Release#verify method to control whether or not fallback to MD5 checksum will be allowed in cases where SHA-256 checksum is not available.

v2.2.9 - 2017-12-01

Changed

• Loosened dependency on faraday and faraday_middleware gems to include recent releases.

v2.2.8 - 2017-11-09

Added

Created PuppetForge::Util class with a single method, version_valid?, in order to drop the r10k dependency on semantic_puppet.

... (truncated)

Commits

• 824ae4b Merge pull request #83 from caseywilliams/maint/prep
• 43d9dab (MAINT) Release prep for v2.3.4
• e1e6f49 Merge pull request #82 from binford2k/update_hostname
• 2268422 (maint) update the Forge api hostname
• 489c156 Merge pull request #81 from aerickson/fix_rb26_warnings
• 7eae637 Merge pull request #80 from aerickson/use_latest_faraday_middleware
• 89c6e54 allow all v14 releases
• b4b361f fix ruby 2.6 warning about "deprecated Object#=~"
• 0670c34 all use of 0.14.0
• 736b945 Merge pull request #79 from caseywilliams/maint/prep
• 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)

[justinstoller]

I'm going to

[dependabot[bot]]

OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version or @dependabot ignore this minor version. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.