search

inspec / train

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

Update chefstyle requirement from 2.1.1 to 2.2.0 #715

Closed dependabot[bot] closed 2 years ago

dependabot[bot] commented 2 years ago

Updates the requirements on chefstyle to permit the latest version.

Changelog

Sourced from chefstyle's changelog.

v2.2.0 (2022-01-05)

Merged Pull Requests

  • Update RuboCop engine to 1.24.1 #153 (tas50)

v2.1.3 (2021-11-15)

Merged Pull Requests

v2.1.2 (2021-10-27)

Merged Pull Requests

v2.1.1 (2021-10-22)

Merged Pull Requests

v2.1.0 (2021-09-30)

Merged Pull Requests

  • Update RuboCop to 1.22 #147 (tas50)
  • Move to GitHub actions for testing #148 (tas50)
  • Enable Bundler/InsecureProtocolSource cop #149 (tas50)

v2.0.9 (2021-08-27)

Merged Pull Requests

v2.0.8 (2021-08-12)

Merged Pull Requests

v2.0.7 (2021-07-24)

Merged Pull Requests

v2.0.6 (2021-07-06)

Merged Pull Requests

  • Update RuboCop engine to 1.18.3 #142 (tas50)

v2.0.5 (2021-06-24)

... (truncated)

Commits
  • d305086 Bump version to 2.2.0 by Chef Expeditor
  • 00157c6 Merge pull request #153 from chef/1.24.1
  • c72bbc6 Vendor rubocop-1.24.1 upstream configuration.
  • 23cfe0e Update to 1.24.1
  • 8b945f7 Update CHANGELOG.md to reflect the promotion of 2.1.3
  • 4fc14a7 Bump version to 2.1.3 by Chef Expeditor
  • b369a45 Merge pull request #152 from chef/1.23
  • 3a1257b Vendor rubocop-1.23.0 upstream configuration.
  • 6de57cd Update RuboCop to 1.23
  • 2f92bd6 Update CHANGELOG.md to reflect the promotion of 2.1.2
  • 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)
chef-expeditor[bot] commented 2 years 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!

dependabot[bot] commented 2 years ago

Superseded by #716.