Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix(deps): update dependency next-seo to v5.13.0 #1436

Merged
merged 1 commit into from
Nov 1, 2022

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Oct 27, 2022

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
next-seo 5.9.0 -> 5.13.0 age adoption passing confidence

Release Notes

garmeeh/next-seo

v5.13.0

Compare Source

Be sure to check out the docs around the app directory

v5.12.0

Compare Source

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.

v5.11.1

Compare Source

Chores

v5.11.0

Compare Source

v5.10.0

Compare Source

feat: add isAccessibleForFree prop on article and newsarticle (https://github.com/garmeeh/next-seo/pull/1060)
fix: article object type BlogPosting (https://github.com/garmeeh/next-seo/pull/1050)


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.

@github-actions
Copy link

github-actions bot commented Oct 27, 2022

📦 Next.js Bundle Analysis

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

🎉 Global Bundle Size Decreased

Page Size (compressed)
global 170.91 KB (🟢 -232 B)
Details

The global bundle is the javascript bundle that loads alongside every page. It is in its own category because its impact is much higher - an increase to its size means that every page on your website loads slower, and a decrease means every page loads faster.

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

If you want further insight into what is behind the changes, give @next/bundle-analyzer a try!

Two Pages Changed Size

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

Page Size (compressed) First Load % of Budget (350 KB)
/ 33.46 KB 204.37 KB 58.39% (+/- <0.01%)
/_error 727 B 171.62 KB 49.03% (+/- <0.01%)
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

The "Budget %" column shows what percentage of your performance budget the First Load total takes up. For example, if your budget was 100kb, and a given page's first load size was 10kb, it would be 10% of your budget. You can also see how much this has increased or decreased compared to the base branch of your 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. If you see "+/- <0.01%" it means that there was a change in bundle size, but it is a trivial enough amount that it can be ignored.

@renovate renovate bot changed the title fix(deps): update dependency next-seo to v5.11.0 fix(deps): update dependency next-seo to v5.11.1 Oct 28, 2022
@renovate renovate bot force-pushed the renovate/next-seo-5.x branch 3 times, most recently from c65f5f6 to 85c38b4 Compare October 30, 2022 18:23
@renovate renovate bot force-pushed the renovate/next-seo-5.x branch from 85c38b4 to fcc0a06 Compare October 31, 2022 16:24
@renovate renovate bot changed the title fix(deps): update dependency next-seo to v5.11.1 fix(deps): update dependency next-seo to v5.13.0 Oct 31, 2022
@Innei Innei merged commit 0dabc7d into master Nov 1, 2022
@renovate renovate bot deleted the renovate/next-seo-5.x branch November 1, 2022 03:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant