From 0f618b87d55808b507d9a623116f62a4df655384 Mon Sep 17 00:00:00 2001 From: Hiroshi SHIBATA Date: Fri, 8 May 2026 18:09:22 +0900 Subject: [ruby/rubygems] Allow non-zero exit status in bundle config gemfile unset spec After 607648d5fc9 (`bundle config get` exits 1 when the value is unset), the spec added in 4658d6bd78b raises in the bundle helper because the new test invokes `config get gemfile` after unsetting it. Co-Authored-By: Claude Opus 4.7 (1M context) --- spec/bundler/commands/config_spec.rb | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/spec/bundler/commands/config_spec.rb b/spec/bundler/commands/config_spec.rb index 0aaae98ccb..e8ab32ca5d 100644 --- a/spec/bundler/commands/config_spec.rb +++ b/spec/bundler/commands/config_spec.rb @@ -605,7 +605,7 @@ RSpec.describe "setting gemfile via config" do bundle "config set gemfile foo/bar_gemfile" bundle "config unset gemfile" - bundle "config get gemfile" + bundle "config get gemfile", raise_on_error: false expect(out).to include("You have not configured a value for `gemfile`") expect(File.read(bundled_app(".bundle/config"))).not_to include("BUNDLE_GEMFILE") -- cgit v1.2.3