Update Chef version requirement from 16+ to 18+ #794
+2
−2
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
After PR #778, the cookbook now requires Chef 18+ due to Ruby 3.1 features, but the documentation still stated Chef 16+. This creates a mismatch between the actual requirements and what users see in the documentation.
Background
PR #778 ("feat: Support PostgreSQL 17") introduced a
.rubocop.yml
file withTargetRubyVersion: 3.1
, which effectively requires Ruby 3.1+ features. The Chef-to-Ruby version mapping is:Since the cookbook now targets Ruby 3.1, it requires Chef 18 or later to function properly.
Changes
metadata.rb
: Changedchef_version
from'>= 16.0'
to'>= 18.0'
README.md
: Changed Chef requirement from "Chef 16" to "Chef 18"This ensures consistency between the cookbook metadata (shown on Chef Supermarket) and the documentation, preventing users from attempting to use the cookbook with incompatible Chef versions.
Fixes #790.
✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.