Repository navigation
Changelog/release discrepancy 3.3.0? #1391
Description
Activity
Hi @justin808, are there any plans to release PR #1363?
At the moment, this issue prevents clients from
react-railsupgrading toconnection_pool >= 3.0. In our case, we needed to bump devise to address the security vulnerability CVE-2026-32700, which in turn required us to add a constraint (gem "connection_pool", "< 3.0") as a workaround because this gem is not compatible with latest version.While this resolves the immediate issue, it’s not an ideal long-term solution. It would be great to know if a release including this fix is planned.
@BookOfGreg @justin808 Any updates on this?
Guys, Let me get on this! Stay tuned! Sorry, been building new documentation sites: reactonrails.com and shakapacker.com.
I was digging in a few months back and CI was blocked.
Reacted by Bauke van Wieren, Leo Diaz and murajun1978@justin808 Thank you! Appreciate it your time on this. I noticed that the PR has been merged; however, the
3.3.0release/tag has not yet been created. We will need to publish this release so it becomes available on RubyGems.@leodiazok finally released. I got a new MacBook, and it's not easy getting all the old dependencies working.
Reacted by Leo Diaz and murajun1978@justin808 Thank you so much! I was able to update successfully. I noticed on the release page the latest release is not up to date, but it seems like the releases are not updated for a while anyways.
If anybody wants help with migration to react_on_rails, please see: https://reactonrails.com/docs/migrating/migrating-from-react-rails.
I was able to get a lot of "one shot prompts."
If anybody wants an upgrade, I can try to do it for $100. Seriously. Just book a meeting: https://meetings.hubspot.com/justingordon/30-minute-consultation.
There seems to be an discrepancy with the CHANGELOG.md, Github tags, and releases on rubygems.
Feb 15 2026 commit cd977b5 updated
CHANGELOG.mdto say av3.3.0released on 2024-11-22 (a date which certainly seems erroneous) withconnection_poolv3 support.The v3.2.1..v3.3.0 comparison shows no difference
Rubygems.org has a most recent version of
v3.2.1.I'm not sure what the intention was, but it is very confusing.