From e4645f5336405dfcb89e3fc8eebbbd06379d5b3d Mon Sep 17 00:00:00 2001
From: Santiago Rodriguez
 <46354312+santiagorodriguez96@users.noreply.github.com>
Date: Mon, 5 Jan 2026 16:58:12 -0300
Subject: [PATCH] ci: avoid passing `enable-frozen-string-literal` flag to ruby

This flag was redundant for our own code since we already have the
`# frozen_string_literal: true` directive at the top of each file,
enforced by RuboCop.

While the flag could theoretically catch frozen string issues in
dependencies, I don't think we want our CI to fail because of frozen
string errors in gems we don't have control of.
---
 .github/workflows/build.yml | 2 --
 1 file changed, 2 deletions(-)

diff --git a/.github/workflows/build.yml b/.github/workflows/build.yml
index 5ea1f463..aea5e528 100644
--- a/.github/workflows/build.yml
+++ b/.github/workflows/build.yml
@@ -70,8 +70,6 @@ jobs:
         bundler-cache: true
 
     - run: bundle exec rspec
-      env:
-        RUBYOPT: ${{ startsWith(matrix.ruby, '3.4') && '--enable=frozen-string-literal' || '' }}
 
   lint:
     runs-on: ubuntu-latest