PR #176 introduced the following dependency constraint in grape-swagger-rails.gemspec:
# Supported Rails versions use JSON APIs removed in JSON 3 (quirks_mode and positional parse options).
spec.add_dependency 'json', '>= 2.0', '< 3.0'
This was necessary at the time because the supported Rails versions depended on JSON APIs that were removed or changed in JSON 3.
Since then, newer Rails versions have been released, including Rails 8.1.x, which is now part of the supported/tested matrix for grape-swagger-rails.
Is the < 3.0 upper bound still necessary for the Rails versions currently supported by this gem?
If not, it would be useful to remove or relax the constraint so applications using newer Rails versions can also upgrade to JSON 3.x without Bundler conflicts.
Related: #176
PR #176 introduced the following dependency constraint in
grape-swagger-rails.gemspec:This was necessary at the time because the supported Rails versions depended on JSON APIs that were removed or changed in JSON 3.
Since then, newer Rails versions have been released, including Rails 8.1.x, which is now part of the supported/tested matrix for
grape-swagger-rails.Is the
< 3.0upper bound still necessary for the Rails versions currently supported by this gem?If not, it would be useful to remove or relax the constraint so applications using newer Rails versions can also upgrade to JSON 3.x without Bundler conflicts.
Related: #176