⬆️ deps: Bump next-seo from 5.4.0 to 5.14.1

[dependabot]

Bumps next-seo from 5.4.0 to 5.14.1.

Release notes

Sourced from next-seo's releases.

v5.14.1

• Adding email property to the ContactPoint type (#1069) f857eb5

garmeeh/next-seo@v5.14.0...v5.14.1

v5.14.0

This release could probably have been a patch release with the below being the only change. Being an SEO library I will always lean towards being extra careful, hence the minor vs patch. Also this could result in broken tests anyway if someone was doing some form of snapshot on the output.

Changes:

• Remove keyoverride attribute from additional meta tags (#1080) 37dda3c

Chores:

• Update app directory documentation (#1078) 0bb10e9
• Bump next from 13.0.0 to 13.0.1 (#1076) 815e636
• Bump @​types/node from 18.11.7 to 18.11.9 (#1077) 7a32471
• Update Docs (#1075) 6b684c1

garmeeh/next-seo@v5.13.0...v5.14.0

v5.13.0

• Next 13 Support (#1074) 4a31018

Be sure to check out the docs around the app directory

garmeeh/next-seo@v5.12.0...v5.13.0

v5.12.0

This release deprecates contactPoints prop on the <OrganizationJsonLd /> component in favour of contactPoint.

You do not need to change anything as until the next major release we will continue to accept contactPoints.

However, it is worth noting that the output script will now contain containPoint as per the correct schema definition. I did consider whether this was a breaking change as if you have tests checking the output they will fail and require a change. If you were effected by this and consider this a breaking change please let me know.

• fix: organization prop contactPoint (#1070) 80dba3d

garmeeh/next-seo@v5.11.1...v5.12.0

v5.11.1

• fix: BreadcrumbJsonLd additional property (#1064) 3ec1251

Chores

• Increase test coverage (#1065) 0144d48

garmeeh/next-seo@v5.11.0...v5.11.1

v5.10.0

feat: add isAccessibleForFree prop on article and newsarticle (garmeeh/next-seo#1060) fix: article object type BlogPosting (garmeeh/next-seo#1050)

... (truncated)

Commits

• d96d58d v5.14.1
• f857eb5 Adding email property to the ContactPoint type (#1069)
• 144c171 v5.14.0
• 37dda3c Remove keyoverride attribute from additional meta tags (#1080)
• 0bb10e9 Update app directory documentation (#1078)
• 815e636 Bump next from 13.0.0 to 13.0.1 (#1076)
• 7a32471 Bump @​types/node from 18.11.7 to 18.11.9 (#1077)
• 6b684c1 Update Docs (#1075)
• a1fab74 v5.13.0
• 4a31018 Next 13 Support (#1074)
• Additional commits viewable in compare view

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 will merge this PR once CI passes on it, as requested by @filiptronicek.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will 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 version will 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 dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[github-actions]

yarn.lock changes

Click to toggle table visibility

Name	Status	Previous	Current
next-seo		5.4.0	5.14.1

[filiptronicek]

@dependabot merge

[github-actions]

📦 Next.js Bundle Analysis

This analysis was generated by the next.js bundle analysis action 🤖

Sixteen Pages Changed Size

The following pages changed size from the code in this PR compared to its base branch:

Page	Size (compressed)	First Load
/	305.28 KB (-16 B)	408.6 KB
/404	211.58 KB (-16 B)	314.9 KB
/500	211.57 KB (-16 B)	314.9 KB
/[code]	219.95 KB (-16 B)	323.27 KB
/_offline	211.6 KB (-16 B)	314.92 KB
/about	179.1 KB (-16 B)	282.42 KB
/admin	966.25 KB (-16 B)	1.04 MB
/auth/login	892.8 KB (-16 B)	996.12 KB
/auth/logout	178.42 KB (-16 B)	281.75 KB
/clip/[code]	480.99 KB (-16 B)	584.31 KB
/clips	314.25 KB (-16 B)	417.57 KB
/file	336.14 KB (-16 B)	439.46 KB
/file/[code]	463.87 KB (-16 B)	567.19 KB
/privacy	180.4 KB (-16 B)	283.72 KB
/receive	304.87 KB (-16 B)	408.19 KB
/settings	948.92 KB (-16 B)	1.03 MB

Details

Only the gzipped size is provided here based on an expert tip.

First Load is the size of the global bundle plus the bundle for the individual page. If a user were to show up to your website and land on a given page, the first load size represents the amount of javascript that user would need to download. If next/link is used, subsequent page loads would only need to download that page's bundle (the number in the "Size" column), since the global bundle has already been downloaded.

Any third party scripts you have added directly to your app using the <script> tag are not accounted for in this analysis

Next to the size is how much the size has increased or decreased compared with the base branch of this PR. If this percentage has increased by 20% or more, there will be a red status indicator applied, indicating that special attention should be given to this.

[dependabot]

Superseded by #1129.