Skip to content

build(deps): update dependency next-plausible to v4#406

Open
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/next-plausible-4.x
Open

build(deps): update dependency next-plausible to v4#406
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/next-plausible-4.x

Conversation

@renovate

@renovate renovate Bot commented Apr 16, 2026

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Change Age Confidence
next-plausible 3.12.54.0.0 age confidence

Release Notes

4lejandrito/next-plausible (next-plausible)

v4.0.0

Compare Source

Full Changelog

Closed issues:


Configuration

📅 Schedule: (in timezone America/Los_Angeles)

  • Branch creation
    • At any time (no schedule defined)
  • Automerge
    • At any time (no schedule defined)

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

Rebasing: Whenever PR becomes conflicted, 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.

@vercel

vercel Bot commented Apr 16, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

1 Skipped Deployment
Project Deployment Actions Updated (UTC)
interval.so Ignored Ignored Jun 13, 2026 8:03pm

Request Review

@renovate renovate Bot force-pushed the renovate/next-plausible-4.x branch 2 times, most recently from f99c093 to b7cd1ad Compare April 17, 2026 10:04
@renovate renovate Bot force-pushed the renovate/next-plausible-4.x branch from b7cd1ad to 0cf58b5 Compare April 29, 2026 12:02
@renovate renovate Bot force-pushed the renovate/next-plausible-4.x branch 2 times, most recently from 8e0dc73 to fe2834d Compare May 18, 2026 09:41
@renovate renovate Bot force-pushed the renovate/next-plausible-4.x branch 2 times, most recently from 350b0b3 to f1e0e1f Compare June 1, 2026 21:10
@renovate renovate Bot force-pushed the renovate/next-plausible-4.x branch from f1e0e1f to 80aeace Compare June 13, 2026 20:03
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