search

interagent / committee

A collection of Rack middleware to support JSON Schema.
MIT License
884 stars 137 forks source link

Update rack requirement from >= 1.5, < 3.1 to >= 1.5, < 3.2 #431

Closed dependabot[bot] closed 1 month ago

dependabot[bot] commented 1 month ago

Updates the requirements on rack to permit the latest version.

Changelog

Sourced from rack's changelog.

[3.1.7] - 2024-07-11

Fixed

[3.1.6] - 2024-07-03

Fixed

  • Fix several edge cases in Rack::Request#parse_http_accept_header's implementation. (#2226, [@​ioquatix])

[3.1.5] - 2024-07-02

Security

[3.1.4] - 2024-06-22

Fixed

  • Fix Rack::Lint matching some paths incorrectly as authority form. (#2220, [@​ioquatix])

[3.1.3] - 2024-06-12

Fixed

[3.1.2] - 2024-06-11

  • Rack::Response will take in to consideration chunked encoding responses (#2204, [@​tenderlove])

[3.1.1] - 2024-06-11

  • Oops! I shouldn't have shipped that

[3.1.0] - 2024-06-11

:warning: This release includes several breaking changes. Refer to the Removed section below for the list of deprecated methods that have been removed in this release.

Rack v3.1 is primarily a maintenance release that removes features deprecated in Rack v3.0. Alongside these removals, there are several improvements to the Rack SPEC, mainly focused on enhancing input and output handling. These changes aim to make Rack more efficient and align better with the requirements of server implementations and relevant HTTP specifications.

SPEC Changes

... (truncated)

Commits
  • 4bb2f72 Bump patch version.
  • 1c1e413 Ignore external tests directory.
  • b4a1036 Prepare for 3.1.7 release.
  • d0da91b Add more external tests.
  • f6f1510 Improve Rack::Response content-length header generation. (#2219)
  • fb339e0 Fix encoding setting for non-binary IO-like objects in MockRequest#env_for
  • e21872d Do not remove escaped opening/closing quotes for content-disposition filenames
  • 5c3d79f Synchronize changelog with HEAD.
  • bca33b4 Allow empty PATH_INFO. (#2214) (#2234)
  • 98aa947 Bump patch version.
  • Additional commits viewable in compare view


Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
geemus commented 1 month ago

@ydah - I think the changes here are the right ones to bring this inline with new rack. I also was able to (locally) downgrade back to the old version of rack to confirm that the updated code still has a passing test suite. So I believe this should be good/safe, but I'd appreciate you taking a look as well when you have a moment. Just let me know if you have any questions or I can clarify anyway. Thanks!

eric-pigeon commented 5 days ago

Can this change be released to ruby gems?

geemus commented 5 days ago

Yes. I'll try to get a release soon, should probably be able to tomorrow (Monday).

geemus commented 4 days ago

@eric-pigeon Ok, thanks for you patience. This should now be available in v5.5.0.