Bump pagy from 9.3.4 to 43.5.3#110
Conversation
Bumps [pagy](https://github.com/ddnexus/pagy) from 9.3.4 to 43.5.3. - [Release notes](https://github.com/ddnexus/pagy/releases) - [Changelog](https://github.com/ddnexus/pagy/blob/master/docs/CHANGELOG.md) - [Commits](ddnexus/pagy@9.3.4...43.5.3) --- updated-dependencies: - dependency-name: pagy dependency-version: 43.5.3 dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: b0c8a55563
ℹ️ About Codex in GitHub
Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".
| nokogiri (1.19.2-x86_64-linux-gnu) | ||
| racc (~> 1.4) | ||
| pagy (9.3.4) | ||
| pagy (43.5.3) |
There was a problem hiding this comment.
Upgrade Pagy call sites alongside major version bump
This lockfile change jumps from Pagy 9.x to 43.x, but the app still uses legacy Pagy APIs (e.g., pagy(@faqs, items: 12) in app/controllers/faqs_controller.rb and include Pagy::Frontend in app/helpers/application_helper.rb). The upstream 43 upgrade guide describes this as a breaking redesign requiring API migration (including new paginator call forms and option names), so leaving code unchanged here is likely to break pagination at runtime when those controller/helper paths execute.
Useful? React with 👍 / 👎.
| pagy (43.5.3) | ||
| json | ||
| uri | ||
| yaml |
There was a problem hiding this comment.
Remove deprecated trim extra before adopting Pagy 43
Pagy 43 deprecates the legacy extras model and explicitly marks trim as discontinued in its upgrade guidance, but this commit updates the gem without removing the active require "pagy/extras/trim" in config/initializers/pagy.rb. That leaves initialization depending on a legacy path no longer part of the supported 43 setup, which can cause boot-time failures or unsupported pagination behavior in production.
Useful? React with 👍 / 👎.
Bumps pagy from 9.3.4 to 43.5.3.
Release notes
Sourced from pagy's releases.
... (truncated)
Changelog
Sourced from pagy's changelog.
... (truncated)
Commits
5f08538Merge branch 'dev'874833cVersion 43.5.34a0fba2💎 Autoload series, a_lambda and page_label55e0802Improve Ferrum test stabilityd9b37f9Improve page segment file876b61f💎 Add Hungarian localization file for Pagy (#896)187e0daMerge branch 'dev'd67d69bVersion 43.5.21f2d27dUpdate libsf3e3342💎 Add type validation for page and limit keys type (close #895)Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)