Skip to content

Update dependency pagy to v43#196

Open
renovate[bot] wants to merge 1 commit intomasterfrom
renovate/pagy-43.x
Open

Update dependency pagy to v43#196
renovate[bot] wants to merge 1 commit intomasterfrom
renovate/pagy-43.x

Conversation

@renovate
Copy link
Copy Markdown
Contributor

@renovate renovate bot commented Jan 4, 2026

This PR contains the following updates:

Package Change Age Confidence
pagy (source, changelog) "~> 9.0""~> 43.0" age confidence

Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.


Configuration

📅 Schedule: Branch creation - "before 2am" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate bot force-pushed the renovate/pagy-43.x branch 2 times, most recently from e852a07 to bb906c7 Compare January 13, 2026 13:39
@renovate renovate bot force-pushed the renovate/pagy-43.x branch 2 times, most recently from 991e897 to a5ff6c0 Compare January 20, 2026 12:48
@renovate renovate bot force-pushed the renovate/pagy-43.x branch 6 times, most recently from 6c278da to 215bec7 Compare January 29, 2026 12:26
@renovate renovate bot force-pushed the renovate/pagy-43.x branch from 215bec7 to f0cae2e Compare February 12, 2026 14:07
@renovate renovate bot force-pushed the renovate/pagy-43.x branch from f0cae2e to 46ae1d6 Compare March 9, 2026 17:20
@renovate
Copy link
Copy Markdown
Contributor Author

renovate bot commented Mar 9, 2026

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: Gemfile
Artifact update for pagy resolved to version 43.4.2, which is a pending version that has not yet passed the Minimum Release Age threshold.
Renovate was attempting to update to 43.2.8
This is (likely) not a bug in Renovate, but due to the way your project pins dependencies, _and_ how Renovate calls your package manager to update them.
Until Renovate supports specifying an exact update to your package manager (https://github.com/renovatebot/renovate/issues/41624), it is recommended to directly pin your dependencies (with `rangeStrategy=pin` for apps, or `rangeStrategy=widen` for libraries)
See also: https://docs.renovatebot.com/dependency-pinning/

@renovate renovate bot force-pushed the renovate/pagy-43.x branch from 46ae1d6 to c16c1f7 Compare March 10, 2026 08:53
@renovate renovate bot changed the title chore(deps): update dependency pagy to v43 Update dependency pagy to v43 Mar 10, 2026
@renovate renovate bot force-pushed the renovate/pagy-43.x branch 3 times, most recently from 1062e6e to 8d81faf Compare March 17, 2026 10:04
@renovate renovate bot force-pushed the renovate/pagy-43.x branch from 8d81faf to e6f4774 Compare March 21, 2026 12:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants