From 62ba96f387155c0bcd2a3eb786fd4b35acd7da54 Mon Sep 17 00:00:00 2001 From: Tim Smith Date: Sat, 27 Jun 2026 22:50:30 -0700 Subject: [PATCH] Drop the logger < 1.6 dependency pin MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The pin was added in July 2024 to dodge logger 1.6.0, which made log levels thread-local by adding state in Logger#initialize and broke Logger subclasses that did not call super. ChefSpec does not require logger anywhere in lib/ — it only arrives transitively via chef — and the modern Chef stack handles current logger correctly. Verified against Chef 19.2.12 / Mixlib::Log 3.2.3 with logger 1.7.0: chefspec loads, Chef::Log works, and the unit suite is green. Remove the pin (and its stale "remedy before Ruby 3.3" comment) so the gem stops holding back logger for its consumers. Signed-off-by: Tim Smith --- chefspec.gemspec | 2 -- 1 file changed, 2 deletions(-) diff --git a/chefspec.gemspec b/chefspec.gemspec index b3719b92..8d8f5a3f 100644 --- a/chefspec.gemspec +++ b/chefspec.gemspec @@ -28,8 +28,6 @@ Gem::Specification.new do |s| s.add_dependency "fauxhai-chef", ">= 9.3" s.add_dependency "rspec", "~> 3.0" - # this needs to be remedied before Ruby 3.3 - s.add_dependency "logger", "< 1.6" s.add_development_dependency "cookstyle", "~> 8.4" # temporary restriction to a version of rspec-expectations that includes the