From 3c8dfc906b85567393587d1ed8d6312e5d991f3d Mon Sep 17 00:00:00 2001
From: Morgan Roderick <morgan@roderick.dk>
Date: Sat, 24 Oct 2026 07:55:44 +0200
Subject: [PATCH] chore: remove stale json 3.x pin comment

The comment explained why json was pinned to 2.x (json 3.0 made
JSON.parse keyword-only, breaking ActiveSupport::JSON.decode). Rails
8.1.4 fixed the positional call and #3051 bumped json to ~> 3.1, so
the pin rationale no longer applies.
---
 Gemfile | 4 ----
 1 file changed, 4 deletions(-)

diff --git a/Gemfile b/Gemfile
index 9603f0c65..bad6f29d0 100644
--- a/Gemfile
+++ b/Gemfile
@@ -35,10 +35,6 @@ gem 'jwt'
 # vips backend is never loaded.
 gem 'image_processing'
 gem 'mini_magick'
-# json 3.0 breaks ActiveSupport::JSON.decode: json 3.0 made JSON.parse
-# keyword-only, so Rails' JSON.parse(json, options) positional-hash call
-# raises ArgumentError and every session-cookie read fails. Pinned until
-# Rails supports json 3.x (https://github.com/codebar/planner/pull/2864).
 gem 'json', '~> 3.1'
 gem 'mutex_m' # LOCKED: Added because of activesupport 7.0
 gem 'nokogiri'