-
Notifications
You must be signed in to change notification settings - Fork 112
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
Updated chef-client to 18.4.2 #3205
Conversation
Signed-off-by: nikhil2611 <[email protected]>
Signed-off-by: nikhil2611 <[email protected]>
Signed-off-by: nikhil2611 <[email protected]>
Signed-off-by: nikhil2611 <[email protected]>
👷 Deploy Preview for chef-workstation processing.
|
Signed-off-by: nikhil2611 <[email protected]>
Signed-off-by: nikhil2611 <[email protected]>
Signed-off-by: nikhil2611 <[email protected]>
Signed-off-by: nikhil2611 <[email protected]>
Signed-off-by: nikhil2611 <[email protected]>
Signed-off-by: nikhil2611 <[email protected]>
Signed-off-by: nikhil2611 <[email protected]>
Signed-off-by: nikhil2611 <[email protected]>
Signed-off-by: nikhil2611 <[email protected]>
Signed-off-by: nikhil2611 <[email protected]>
SonarQube Quality Gate |
Quality Gate passedIssues Measures |
SonarQube Quality Gate |
Quality Gate passedIssues Measures |
Why wouldn't we upgrade to the latest stable 18.4.12 especially since it's just a patch release version difference. https://docs.chef.io/release_notes_client/ |
Hey @Stromweld, We are upgrading the Chef to latest(18.4.12) for this release, you can find the changes in #3222 PR. |
Description
Updated chef-client to latest version - 18.4.2
Related Issue
Types of changes
Checklist:
Gemfile.lock
has changed, I have used--conservative
to do it and included the full output in the Description above.