search

inspec / train

Transport Interface to unify communication over SSH, WinRM, and friends.
Apache License 2.0
119 stars 87 forks source link

Update mocha requirement from ~> 1.1 to ~> 2.1 #748

Closed dependabot[bot] closed 11 months ago

dependabot[bot] commented 1 year ago

Updates the requirements on mocha to permit the latest version.

Changelog

Sourced from mocha's changelog.

2.1.0

External changes

Internal changes

  • Update URLs for links to Ruby & MIT licenses (d6470af4)

2.0.4

Internal changes

  • Update README.md (e8c21e1b)

2.0.3

External changes

Internal changes

  • Add Ruby v3.1 to the CircleCI build (3e460489)
  • DRY up regexp_matches test (ae9fed4a)
  • Fix regexp_matches tests in Ruby v3.2 (26b106a5, #590)
  • Use Ruby 1.9 hash syntax (8bc0ad2f, #598, #537) - thanks to @​herwinw
  • Simplify storage of MOCHA_OPTIONS (b70507a1, #600) - thanks to @​herwinw
  • Pin JRuby to v9.3.9.0 in CircleCI builds (b8e6d064, #591)
  • Rubocop: enable Style/FormatStringToken cop (089a688e, #603) - thanks to @​herwinw
  • Remove Ruby version check from RespondsLikeTest (21583129)
  • Add Ruby v3.2 to CircleCI build (f7e17636, #601)
  • Use Ruby v2.6 vs v2.2 to run lint CI job (af40b7db)
  • Pin yard version to v0.9.28 to avoid ArgumentError (12f1eef7)
  • Revert "Pin JRuby to v9.3.9.0 in CircleCI builds" (4f5bb2f0, #591)
  • Remove invalid CircleCI token from badge URL (7078e76a)
  • Revert "Pin yard version to v0.9.28 to avoid ArgumentError" (7c6c10c5, #609)
  • Remove Google Analytics tracking code (2279c49d, #612)
  • Update MIT-LICENSE.md (48162b4e)
  • Update COPYING.md (f3152376)

2.0.2

External changes

2.0.1

... (truncated)

Commits
  • 25ed0e5 [skip ci] Update documentation for v2.1.0
  • f65a747 Bump version to 2.1.0 & prepare for release
  • 32ef48f Fix Mocha/Minitest compatibility
  • d6470af Update URLs for links to Ruby & MIT licenses
  • 345f042 [skip ci] Update documentation for v2.0.4.
  • d07c1f6 Bump version to 2.0.4 & prepare for release
  • e8c21e1 Update README.md
  • f409e3a [skip ci] Update documentation for v2.0.3.
  • ddef48f Bump version to 2.0.3 & prepare for release
  • f315237 Update COPYING.md
  • Additional commits viewable in compare view


You can trigger a rebase of this PR 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)

Note Automatic rebases have been disabled on this pull request as it has been open for over 30 days.

chef-expeditor[bot] commented 1 year ago

Hello dependabot[bot]! Thanks for the pull request!

Here is what will happen next:

  1. Your PR will be reviewed by the maintainers.
  2. Possible Outcomes a. If everything looks good, one of them will approve it, and your PR will be merged. b. The maintainer may request follow-on work (e.g. code fix, linting, etc). We would encourage you to address this work in 2-3 business days to keep the conversation going and to get your contribution in sooner. c. Cases exist where a PR is neither aligned to Chef InSpec's product roadmap, or something the team can own or maintain long-term. In these cases, the maintainer will provide justification and close out the PR.

Thank you for contributing!