From 3f751bc0ec1ac425eb51f73e4b753942183d3974 Mon Sep 17 00:00:00 2001 From: tlarrain Date: Thu, 27 Aug 2026 12:55:46 -0400 Subject: [PATCH] ci(release): run release job on Ruby 3.4 rubygems/release-gem enables attestations by default, which preloads a patch via RUBYOPT that requires rubygems/commands/push_command before Bundler.setup runs. That activates Ruby's default securerandom, and Bundler then aborts because Gemfile.lock pins 0.4.1 (activesupport 8.0, pulled in through money-rails, requires securerandom >= 0.3). Ruby 3.2 ships securerandom 0.2.2 and 3.3 ships 0.3.1, so both conflict; 3.4 ships 0.4.1 and matches the lockfile. The release job only builds and pushes the gem, so it does not need to run on the minimum supported Ruby version. CI still covers 3.2, 3.3 and 3.4. --- .github/workflows/release.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/.github/workflows/release.yml b/.github/workflows/release.yml index 1072bd1..83aa108 100644 --- a/.github/workflows/release.yml +++ b/.github/workflows/release.yml @@ -26,7 +26,7 @@ jobs: - uses: ruby/setup-ruby@v1 with: - ruby-version: '3.2.2' + ruby-version: '3.4' bundler-cache: true - run: bundle exec rspec