You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There seems to be an discrepancy with the CHANGELOG.md, Github tags, and releases on rubygems.
Feb 15 2026 commit cd977b5 updated CHANGELOG.md to say a v3.3.0 released on 2024-11-22 (a date which certainly seems erroneous) with connection_pool v3 support.
At the moment, this issue prevents clients from react-rails upgrading to connection_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.
@justin808 Thank you! Appreciate it your time on this. I noticed that the PR has been merged; however, the 3.3.0 release/tag has not yet been created. We will need to publish this release so it becomes available on RubyGems.
@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.
Activity
salimhb commentedon Mar 9, 2026
Agree with the above. It would be good to have #1367 in a new release.
leodiazok commentedon Mar 20, 2026
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.
baukevw commentedon Mar 25, 2026
@BookOfGreg @justin808 Any updates on this?
justin808 commentedon Mar 27, 2026
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.
leodiazok commentedon Mar 30, 2026
@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.justin808 commentedon Mar 31, 2026
@leodiazok finally released. I got a new MacBook, and it's not easy getting all the old dependencies working.
baukevw commentedon Mar 31, 2026
@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.
ivailop commentedon Mar 31, 2026
Also the CHANGELOG has a wrong date
3.3.0 - 2024-11-22
justin808 commentedon Apr 3, 2026
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.