[ruby] Update pagy 6.4.3 → 7.0.11 (major)

[depfu[bot]]

Here is everything you need to know about this upgrade. Please take a good look at what changed and the test results before merging this pull request.

What changed?

✳️ pagy (6.4.3 → 7.0.11) · Repo · Changelog

Release Notes

7.0.5 (from changelog)

• Updated gems, npm modules, contributors
• Added the pagy stylesheets to the gem, updated apps, docs and manifest
• Added note for the metrics and compacted the chart section (closes #652)
• Docs: fix formatting, grammar in README.md (#654)
• Add note about PR base branches to readme (#653)

7.0.4 (from changelog)

• Tailwind styles integrated with the pagy-items-selector-js (#646)
• Deprecated the "pagination" CSS class, use the "pagy" CSS class that has been added to all the interactive pagy helper outputs
• Fix indentation of cs locale (#648); add "pagy.aria_label.nav.few" entry, duplicating the "other" pluralization
• Update cs translations (#648)
• Expand/Correct changes about pagy.prev and pagy.next (#649)

7.0.3 (from changelog)

• Remove extra space in pagy_nav, pagy_nav_js and .pagy-combo-input
• Refactor of tailwind styles and docs (closes #646)
• Add pagy_tailwind_app.ru (#646)
• Add missing CSS breaking change to the CHANGELOG (#646)

7.0.2 (from changelog)

• Fix for missing to fetch count_args default (close #645)
• Non-code improvements

7.0.1 (from changelog)

• Updates ckb translations to be complaint with ARIA in v7.x.x (#643)

7.0.0

✴ What's new ✴

• JSON:API support
• ARIA compliance and refactoring of dictionary files
• Added a simpler and faster nav without gaps (just pass an integer to the :size)
• Pagy follows the ruby end-of-life supported rubies now (3.1+)
• See the Changelog for possible breaking changes

Does any of this look wrong? Please let us know.

Commits

See the full diff on Github. The new version differs by more commits than we can show here.

---

👉 No CI detected

You don't seem to have any Continuous Integration service set up!

Without a service that will test the Depfu branches and pull requests, we can't inform you if incoming updates actually work with your app. We think that this degrades the service we're trying to provide down to a point where it is more or less meaningless.

This is fine if you just want to give Depfu a quick try. If you want to really let Depfu help you keep your app up-to-date, we recommend setting up a CI system:

* [Circle CI](https://circleci.com), [Semaphore ](https://semaphoreci.com) and [Github Actions](https://docs.github.com/actions) are all excellent options. * If you use something like Jenkins, make sure that you're using the Github integration correctly so that it reports status data back to Github. * If you have already set up a CI for this repository, you might need to check your configuration. Make sure it will run on all new branches. If you don’t want it to run on every branch, you can whitelist branches starting with `depfu/`.

---

Depfu will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with @depfu rebase.

All Depfu comment commands

@​depfu rebase

Rebases against your default branch and redoes this update

@​depfu recreate

Recreates this PR, overwriting any edits that you've made to it

@​depfu merge

Merges this PR once your tests are passing and conflicts are resolved

@​depfu cancel merge

Cancels automatic merging of this PR

@​depfu close

Closes this PR and deletes the branch

@​depfu reopen

Restores the branch and reopens this PR (if it's closed)

@​depfu pause

Ignores all future updates for this dependency and closes this PR

@​depfu pause [minor|major]

Ignores all future minor/major updates for this dependency and closes this PR

@​depfu resume

Future versions of this dependency will create PRs again (leaves this PR as is)