Skip to content
This repository was archived by the owner on Feb 9, 2024. It is now read-only.

Update dependency next-seo to v6#211

Open
renovate[bot] wants to merge 1 commit intomainfrom
renovate/next-seo-6.x
Open

Update dependency next-seo to v6#211
renovate[bot] wants to merge 1 commit intomainfrom
renovate/next-seo-6.x

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Apr 4, 2023

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
next-seo 5.14.0 -> 6.4.0 age adoption passing confidence

Release Notes

garmeeh/next-seo (next-seo)

v6.4.0

Compare Source

v6.3.0

Compare Source

Misc

v6.2.0

Compare Source

v6.1.0

Compare Source

v6.0.0: V6

Compare Source

Breaking change:

If you are using the app directory you will need to migrate from NextSeo component to the built in generateMetaData method in Next.js

Notes:

For standard meta data (eg: , <title>) then it is highly recommended that you use the built in generateMetaData method. You can check out the docs here

For JSON-LD then the only change needed is you should add useAppDir={true} to the JSON-LD component in use. You should add use this component in your page.js and NOT your head.js.

Also better safe than sorry with SEO 😅

As this bug was fixed via #​1062 it may have some strange effects if you have a work around in place.

All other changes:

v5.15.0

Compare Source

v5.14.1

Compare Source


Configuration

📅 Schedule: 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 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 has been generated by Mend Renovate. View repository job log here.

@vercel
Copy link

vercel bot commented Apr 4, 2023

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
website ❌ Failed (Inspect) Oct 31, 2023 9:53pm

@renovate renovate bot added the renovate label Apr 4, 2023
@renovate
Copy link
Contributor Author

renovate bot commented Apr 4, 2023

⚠ 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: package-lock.json
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR! 
npm ERR! While resolving: echo-karriere@3.0.0
npm ERR! Found: tailwindcss@2.2.19
npm ERR! node_modules/tailwindcss
npm ERR!   dev tailwindcss@"2.2.19" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer tailwindcss@">=3.0.0 || >= 3.0.0-alpha.1" from @tailwindcss/forms@0.5.4
npm ERR! node_modules/@tailwindcss/forms
npm ERR!   dev @tailwindcss/forms@"0.5.4" from the root project
npm ERR! 
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR! 
npm ERR! 
npm ERR! For a full report see:
npm ERR! /tmp/worker/aa7014/87901f/cache/others/npm/_logs/2023-10-31T21_53_21_424Z-eresolve-report.txt

npm ERR! A complete log of this run can be found in: /tmp/worker/aa7014/87901f/cache/others/npm/_logs/2023-10-31T21_53_21_424Z-debug-0.log

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants