all releases all gems

minor release

3.34.0

avo gem · info and install
avo

Release notes

For more information and the release video check out the full release page

🎸 Features

Before you upgrade

Avo 3 no longer sets an upper bound on pagy, so bundle update avo can move your app from pagy 9 to pagy 43. Most apps need nothing else. Add a line to your Gemfile first if one of these applies to your app.

If your app Add to your Gemfile
Runs on Rails 8.0, 7.1, 7.0 or 6.1, or on Rails 7.2 below 7.2.4 gem "json", "< 3"
Calls pagy in its own code (Pagy::Backend, Pagy::Frontend, pagy_nav) gem "pagy", "~> 9.4"
Follows the REST API integration guide (pagy_get_items, pagy_get_vars) gem "pagy", "~> 9.4"
Runs on Ruby 3.2 gem "pagy", "~> 9.4"

Pagy 43 depends on json, and json 3 makes the JSON encoder of those Rails versions raise ArgumentError. Pagy 43 also removed Pagy::Backend, Pagy::Frontend and the pagy 9 helpers, and it no longer calls pagy_get_items or pagy_get_vars. On Ruby 3.2, Bundler stops at pagy 43.4.4, which is affected by GHSA-2xmw-f8j8-wfxc. Avo's own pagination isn't exposed to it, but your own code might be.

If you ejected Avo::PaginatorComponent, replace helpers.pagy_info and helpers.pagy_nav in your copy with helpers.avo_pagy_info and helpers.avo_pagy_nav. Apps on Ruby 3.1 stay on pagy 9.4 on their own.

The 3.34.0 upgrade guide covers every case in detail.

🚨 Security

🤖 Maintenance

  • fix(3.x): remove unused resource_table and resource_grid helpers @Paul-Bob (avo v.3.33.4 #4961)

Dependency changes

- pagy (>= 7.0.0, < 43)
+ pagy (>= 7.0.0)
Avo is just awesome. We migrated our custom admin dashboard within a few weeks...
It saved us hundreds of hours of development work and we could focus on our main business!
We love the quick (and awesome) support and the weekly release cycle with great updates.
A real game changer! :)
Jonas Reif
Jonas Reif
Co-Founder, Upspeak.de

latest minor release

Avo v4.4.0 released about 17 hours ago.