Added Rack 3.1 to the list of Rack versions we test against.

.circleci/config.yml

@@ -28,4 +28,4 @@ workflows:
           matrix:
             parameters:
               ruby_version: ["3.1", "3.2", "3.3"]
-              rack_version: ["2.2.0", "3.0.0"]
+              rack_version: ["2.2.0", "3.0.0", "3.1.0"]

.github/workflows/ci.yml

@@ -19,6 +19,7 @@ jobs:
         rack_version:
           - "2.2.0"
           - "3.0.0"
+          - "3.1.0"
     name: Ruby ~> ${{ matrix.ruby_version }}; Rack ~> ${{ matrix.rack_version }}
     runs-on: ubuntu-latest
     env:

features/skip_some_routes.feature

@@ -56,7 +56,7 @@ Feature: Skipping the check for some specific routes
       | PUT    | /this/one/too                   |
       | DELETE | /this/one/too                   |
 
-  Scenario Outline: Handling correctly empty PATH_INFO
+  Scenario Outline: Handling correctly empty PATH_INFO when using Rack 3.0 and earlier
     Given a rack with the anti-CSRF middleware and the :skip option
       | pair     |
       | POST:/   |

features/step_definitions/request_steps.rb

@@ -48,9 +48,11 @@
   end
 end
 
+# Rack 3.1 changed spec so that now PATH_INFO cannot be empty. Below we cheat
+# a bit and change PATH_INFO when using Rack 3.1+
 When /^it receives a (.*) request with neither PATH_INFO nor CSRF token or header$/ do |http_method|
   begin
-    @browser.request '/doesntmatter', :method => http_method, 'PATH_INFO' => ''
+    @browser.request '/doesntmatter', :method => http_method, 'PATH_INFO' => (Rack.release >= '3.1.0' ? '/' : '')
   rescue StandardError => e
     @exception = e
   end