From 26767a726363dc65949b519da3a62cd8574767b6 Mon Sep 17 00:00:00 2001
From: KJ Tsanaktsidis <ktsanaktsidis@zendesk.com>
Date: Tue, 9 Jan 2024 08:44:13 +1100
Subject: [PATCH] Run Rubocop against Ruby 3.2

There's no reason to run Rubocop against such an old version of Ruby;
it's perfectly capable of parsing code according to Ruby 2.6 rules even
when running on a more modern ruby (`TargetRubyVersion` in rubocop.yml).
So, just run it on Ruby 3.2.
---
 .github/workflows/test.yaml | 8 ++------
 1 file changed, 2 insertions(+), 6 deletions(-)

diff --git a/.github/workflows/test.yaml b/.github/workflows/test.yaml
index e263e5d0b..cad1d9b9f 100644
--- a/.github/workflows/test.yaml
+++ b/.github/workflows/test.yaml
@@ -18,12 +18,8 @@ jobs:
       - name: Set up Ruby
         uses: ruby/setup-ruby@v1
         with:
-          ruby-version: "2.6"
-      - name: Set up Gems
-        run: |
-          gem update --system --no-document
-          gem install bundler --no-document
-          bundle install --jobs 4 --retry 3 --path=.bundle
+          ruby-version: "3.2"
+          bundler-cache: true
       - name: Lint
         run: bundle exec rubocop