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

Update chef gems need to refer chef-17 #1772

Merged
merged 1 commit into from
Nov 3, 2022

Conversation

vkarve-chef
Copy link
Collaborator

Signed-off-by: Vikram Karve vikram.karve@progress.com

Description

Ohai 17.x should be in sync with Chef 17.x. The chef-util and chef-config gem dependencies should refer the chef-17 branch of github.com/chef/chef

Related Issue

Doesn't fix #1771 but perhaps related.

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)
  • Chore (non-breaking change that does not add functionality or fix an issue)

Checklist:

  • I have read the CONTRIBUTING document.
  • I have run the pre-merge tests locally and they pass.
  • I have updated the documentation accordingly.
  • I have added tests to cover my changes.
  • All new and existing tests passed.
  • All commits have been signed-off for the Developer Certificate of Origin.

Signed-off-by: Vikram Karve <vikram.karve@progress.com>
@vkarve-chef vkarve-chef requested review from a team as code owners October 26, 2022 07:59
@sonarcloud
Copy link

sonarcloud bot commented Oct 26, 2022

Kudos, SonarCloud Quality Gate passed!    Quality Gate passed

Bug A 0 Bugs
Vulnerability A 0 Vulnerabilities
Security Hotspot A 0 Security Hotspots
Code Smell A 0 Code Smells

No Coverage information No Coverage information
No Duplication information No Duplication information

@vkarve-chef vkarve-chef merged commit 8067c29 into 17-stable Nov 3, 2022
@vkarve-chef vkarve-chef deleted the vkarve/update-chef-gem-dep branch November 3, 2022 06:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants