Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bump kitchen-vagrant from 1.14.1 to 2.0.0 in /omnibus #6974

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

dependabot[bot]
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Feb 16, 2024

Bumps kitchen-vagrant from 1.14.1 to 2.0.0.

Release notes

Sourced from kitchen-vagrant's releases.

v1.14.2

1.14.2 (2023-11-27)

Bug Fixes

Changelog

Sourced from kitchen-vagrant's changelog.

2.0.0 (2024-02-14)

  • Require Vagrant 2.4 or later
  • Drop support for EOL Ruby 2.7 release
  • Add a new box_arch configuration option for defining the architecture to use
  • Eliminate the need for the vagrant-winrm plugin on Windows boxes

1.14.2 (2023-11-27)

Bug Fixes

Commits

Dependabot compatibility score

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 show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @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.

Bumps [kitchen-vagrant](https://github.com/opscode/kitchen-vagrant) from 1.14.1 to 2.0.0.
- [Release notes](https://github.com/opscode/kitchen-vagrant/releases)
- [Changelog](https://github.com/test-kitchen/kitchen-vagrant/blob/main/CHANGELOG.md)
- [Commits](test-kitchen/kitchen-vagrant@v1.14.1...v2.0.0)

---
updated-dependencies:
- dependency-name: kitchen-vagrant
  dependency-type: direct:development
  update-type: version-update:semver-major
...

Signed-off-by: dependabot[bot] <[email protected]>
@dependabot dependabot bot requested a review from a team as a code owner February 16, 2024 04:11
@dependabot dependabot bot added the dependencies Pull requests that update a dependency file label Feb 16, 2024
@dependabot dependabot bot requested review from Vasu1105 and Nik08 February 16, 2024 04:11
Copy link

netlify bot commented Feb 16, 2024

Deploy Preview for chef-inspec canceled.

Name Link
🔨 Latest commit d1b8cbb
🔍 Latest deploy log https://app.netlify.com/sites/chef-inspec/deploys/65cee076e193820008109c81

Copy link
Contributor

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!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Pull requests that update a dependency file
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

0 participants