Upgrading kaminari 0.17 to 1
Breaking0.17.0 → 1.3.2Breaking2Security3Platform2Deprecated1New7Changed15Fixed29
Fetching 12 releases from GitHub…6 / 12
Security`page` ignores a Hash or Array page number such as `?page[]=1` instead of raising an error.#1087 ↗
BreakingUpgrade verdict
2 breaking changes and 2 platform requirement changes and 3 security fixes.
In plain terms
- The default pagination summary text now uses an en dash between the first and last entry numbers.
- Requesting a page past the last page now shows "No entries found" rather than a nonsensical range.
- The gem no longer runs on Ruby 2.0.
- The gem now works with newer Ruby versions.
Must act Top 5 of 8 that need code or config changes
Ruby requirement changed in 1.0.1: >= 0 → >= 2.0.0.
What you must change
Breaking2
The default English
page_entries_info message separates the range with an en dash (e.g. "1 - 25") instead of - .page_entries_infopage_entries_info displays "No entries found" on out of range pages instead of an inverted range like "Displaying users 81 - 80 of 50 in total".page_entries_infoSecurity3
page ignores a Hash or Array page number such as ?page[]=1 instead of raising an error.pagepage_entries_info escapes entry_name, which could contain user input, while leaving an html_safe entry_name unchanged.page_entries_infoentry_namehtml_safeAdds
original_script_name parameter to the ignore list, addressing CVE-2020-11082.original_script_nameModerate · CVSS 6.4Platform2
Drops Ruby 2.0 support.
Adds support for Ruby 3.1, 3.2, 3.3, 3.4, and 4.0.
Deprecations to plan for
Deprecated1
Deprecates
current_per_page in favor of limit_value.current_per_pagelimit_value