v1.13.0

What's Changed

• [CLI] Support the PORT ENV variable by @TheBlackArroVV in #124
• Add the RequestId middleware in #127
• Correctly handle persistent HTTP connections in #128
• [Cable] Improve the time to connect in #129

Shoutouts

Special thanks to @p8 for tackling the Ruby 3.4 + Rage bug!

New Contributors

• @TheBlackArroVV made their first contribution in #124

Full Changelog: v1.12.0...v1.13.0

v1.12.0

What's Changed

• [Cable] Added Redis adapter, which now allows you to scale Rage::Cable applications to more than one server. The adapter is based on Redis Streams, which means clients do not lose messages during network disruptions. As before, an adapter is not needed if you only use one server. This means that even if Redis is down due to an outage, clients connected to the same server as the broadcaster will still receive broadcasts.
• [API] Added long-awaited around_action hooks.
• [OpenAPI] Added global response tags, which can be used to specify global responses shared by multiple endpoints.

Full Changelog: v1.11.0...v1.12.0

v1.11.0

What's Changed

If you still haven’t had enough reasons to use Rage, here’s one more - v1.11 now lets you build OpenAPI specifications for your applications!

We’ve worked hard on implementing this feature and even harder on scoping it out. And with features like automatic security scheme application based on before_action callbacks and integration with the awesome Alba, we couldn’t be happier with the result!

So, check out the guide and don’t forget to share your feedback!

Another important update in this release:
Rage now correctly handles ActiveRecord connections in the environments with legacy_connection_handling == false.

Full Changelog: v1.10.1...v1.11.0

v1.10.0

What's Changed

v1.10.0 focuses on the database and brings two major changes:

• Rage's own Connection Pool is now enabled by default. We've implemented lots of improvements and stability fixes to it while preserving excellent performance. Active Record versions starting with 6.0 are supported.
• You can now use the -d option with the rage new command to preconfigure the app for the selected database. Thanks to standalone_migrations, commands like rage db:migrate or rage db:seed are supported out-of-the-box.

Other changes in the release:

• Add rage middleware and rage version commands.
• Log to STDOUT by default in production.

Full Changelog: v1.9.0...v1.10.0

v1.9.0

What's Changed

• Allow to serve static files from the public directory in #100
• Add request methods to the Rage::Request class by @cuneyter in #97
• Correctly set Rails env in #102
• Rails 7.2 compatibility in #101

Full Changelog: v1.8.0...v1.9.0

v1.8.0

What's Changed

v1.8.0 adds support for WebSockets! Head out to the WebSockets page to see it in action. Make sure to check the benchmarks!

On the note of benchmarks, Rage is now part of the TechEmpower benchmark project! And we all look forward to seeing the official results 😬🤩

Full Changelog: v1.7.0...v1.8.0

v1.7.0

What's Changed

• Controller parameters wrapping feature by @alex-rogachev in #89
• Unknown Environment Error Handling by @cuneyter in #95
• Allow rescue_from handlers to not accept arguments in #93

New Contributors

• @cuneyter made their first contribution in #95

Full Changelog: v1.6.0...v1.7.0

v1.6.0

What's Changed

• Improve Rage.multi_application.
  • Rage now correctly handles internal Rails routes, e.g. /rails/action_mailbox/relay/inbound_emails.
• Support legacy root helpers.
  • Rage now supports legacy root helpers, e.g. get "/photos/:id" => "photos#show" or get "search" => :index.

Full Changelog: v1.5.1...v1.6.0

v1.0.0

The first production-ready release of Rage is out! 🎉

We have implemented a lot of exciting features, and there is still more to come! Thank you to all the contributors and folks who provided extremely valuable feedback! Unfortunately, I can’t thank my wife as she beats me with her little fists every time I try to work on this project. But, hopefully, we will figure it out before v2 is out.