-
Notifications
You must be signed in to change notification settings - Fork 167
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support for Rack v3 #232
Comments
Sounds reasonable to me. Let's do this once #243 is merged |
Does this mean the people working on this gem will be looking at rack3 support? Also is there a reason the changelog is over 4 years out of date? Do you know if there is a plan to maintain the changelog again @mnovelo |
@luke-hill yes, we'll look into rack3 support. If you've got a PR for that, that'd be helpful! I just started as a maintainer about a week ago, but the changelog is definitely something I'm looking forward to updating and keeping updated. |
Hi @mnovelo - Is there any movement on this. Do we think this is something that will happen this Summer? In 2024? e.t.c.? |
This summer yes. The priority is to get the specs passing again first |
just merged #253 ! Now just checking everything is looking good in prep for releasing a new version! |
Hi,
There's currently a Web Cache Poisoning vulnerability in Rack >
v3.0
Its been out for a while and Rack released a major version bump to address it in
v3.0.0
Rails has also added support for Rack >
v3.0
in the upcomingv7.1.0
releaserack >= 3
in Rails. rails/rails#46594 (comment)However, the
ros-apartment
gem is pinned torack < 3.0
which prevents us from upgrading to the latest version ofrack
Best I can tell is that this was introduced here out of precaution:
#24
Any chance this could be bumped up to
rack < 4.0
?Let me know if there's something I can help with -- I'd be happy to submit a PR if this is just a matter of updating the gemspec and running tests.
The text was updated successfully, but these errors were encountered: