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 to v14 #1177

Merged
merged 2 commits into from
Jan 20, 2024
Merged

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Oct 27, 2023

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
next (source) ^13.5.6 -> ^14.1.0 age adoption passing confidence

Release Notes

vercel/next.js (next)

v14.1.0

Compare Source

v14.0.4

Compare Source

v14.0.3

Compare Source

v14.0.2

Compare Source

v14.0.1

Compare Source

Core Changes
  • Add Next.js 14 codemods to CLI output.: #​57552
  • OpenTelemetry: propagate a configured context(s) to root requests: #​57084
  • debug: Add tags to next build traces to track build configuration in the .next/trace file: #​56965
  • [Traces] Await the flush of the trace write stream to make sure trace file is written: #​57641
  • Add node-pty to externals list: #​57640
  • fix: move logging config validation out of experimental: #​57530
  • Update font data: #​57728
  • Support viewport export via TS Plugin: #​57554
  • Fix: Build compilation warning when using middleware: #​57685
  • chore: Update flight-client-entry-plugin.ts typo: #​57734
  • Improve error for missing default export in dynamic metadata routes: #​57711
  • fix gsp tracing issue: #​57766
  • fix(turbopack): don't match empty route groups: #​57647
  • Update React from 8c8ee9e to 0c63487 and types: #​57772
Documentation Changes
  • Add missing dot in codemod command: #​57536
  • docs(fix): example text unescaped entities: #​57255
  • doc: Clarify built-in support for sass after installation: #​57279
  • Update docs with a Good to know box about using redirect in client components: #​56966
  • docs: fix 02-dynamic-routes.mdx: #​57029
  • Fix incorrect link in GTM docs: #​57547
  • Fix typos: #​57592
  • Add apostrophe 07-error-handling.mdx: #​57626
  • Fix: codemods.mdx Incorrect heading structure of next-og-import, meta…: #​57605
  • Typo fix, version "13" to "14": #​57723
  • Fix Google Tag Manager URL in Third Party Libraries documentation: #​57731
Example Changes
Misc Changes
  • update manifest: #​57523
  • update next/third-parties to use Next 14 or 13 as a peer dependency, instead of just 13: #​57515
  • Modify tailwindcss related dependency of create-next-app: #​57262
  • Remove extra CI step and lock Node.js version: #​57769
Credits

Huge thanks to @​dijonmusters, @​sokra, @​philwolstenholme, @​IgorKowalczyk, @​housseindjirdeh, @​Zoe-Bot, @​HanCiHu, @​JackHowa, @​goncy, @​hirotomoyamada, @​pveyes, @​yeskunall, @​vinaykulk621, @​ChendayUP, @​leerob, @​dvoytenko, @​mknichel, @​ijjk, @​hmaesta, @​ajz003, @​its-kunal, @​joelhooks, @​blurrah, @​tariknh, @​Vinlock, @​Nayeem-XTREME, @​aziyatali, @​aspehler, @​huozhi, @​ztanner, @​ForsakenHarmony, @​moka-ayumu, and @​gnoff for helping!

v14.0.0

Compare Source


Configuration

📅 Schedule: Branch creation - "every weekend" in timezone Asia/Shanghai, Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

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

@vercel
Copy link

vercel bot commented Oct 27, 2023

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

Name Status Preview Comments Updated (UTC)
blog ✅ Ready (Inspect) Visit Preview 💬 Add feedback Jan 20, 2024 4:54am

@renovate renovate bot added the dependencies Pull requests that update a dependency file label Oct 27, 2023
@renovate renovate bot requested a review from sabertazimi October 27, 2023 18:44
@github-actions
Copy link
Contributor

github-actions bot commented Oct 27, 2023

Lighthouse Report

https://blog-914xojp65-sabertaz.vercel.app/

🚀 Vercel preview deployment
Lighthouse report

Category Score
🟢 performance 96
🟢 accessibility 100
🟢 best-practices 92
🟢 seo 100
🟢 pwa 100

https://blog-914xojp65-sabertaz.vercel.app/posts

🚀 Vercel preview deployment
Lighthouse report

Category Score
🟢 performance 98
🟢 accessibility 92
🟢 best-practices 92
🟢 seo 100
🟢 pwa 100

https://blog-914xojp65-sabertaz.vercel.app/tags

🚀 Vercel preview deployment
Lighthouse report

Category Score
🟢 performance 100
🟢 accessibility 92
🟢 best-practices 92
🟢 seo 100
🟢 pwa 100

https://blog-914xojp65-sabertaz.vercel.app/books

🚀 Vercel preview deployment
Lighthouse report

Category Score
🟢 performance 100
🟢 accessibility 92
🟢 best-practices 92
🟢 seo 100
🟢 pwa 100

https://blog-914xojp65-sabertaz.vercel.app/about

🚀 Vercel preview deployment
Lighthouse report

Category Score
🟢 performance 99
🟢 accessibility 92
🟢 best-practices 92
🟢 seo 100
🟢 pwa 100

@codecov
Copy link

codecov bot commented Oct 27, 2023

Codecov Report

All modified and coverable lines are covered by tests ✅

Comparison is base (65686fc) 98.45% compared to head (d561b66) 98.49%.

❗ Current head d561b66 differs from pull request most recent head adcf41b. Consider uploading reports for the commit adcf41b to get more accurate results

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #1177      +/-   ##
==========================================
+ Coverage   98.45%   98.49%   +0.04%     
==========================================
  Files         175      175              
  Lines         839      863      +24     
  Branches       86       86              
==========================================
+ Hits          826      850      +24     
  Misses         10       10              
  Partials        3        3              

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@renovate renovate bot force-pushed the renovate/major-nextjs branch 2 times, most recently from f0574f9 to 3e7a867 Compare December 30, 2023 09:16
@renovate renovate bot force-pushed the renovate/major-nextjs branch from 3e7a867 to b015862 Compare December 30, 2023 19:54
@renovate renovate bot force-pushed the renovate/major-nextjs branch from b015862 to f7d2dad Compare January 5, 2024 19:01
@renovate renovate bot force-pushed the renovate/major-nextjs branch from f7d2dad to 0628d98 Compare January 6, 2024 01:28
@renovate renovate bot force-pushed the renovate/major-nextjs branch from 0628d98 to 8366089 Compare January 6, 2024 17:12
@renovate renovate bot force-pushed the renovate/major-nextjs branch from 8366089 to 6933697 Compare January 13, 2024 02:03
@renovate renovate bot force-pushed the renovate/major-nextjs branch from 6933697 to 9547a5b Compare January 15, 2024 08:44
@renovate renovate bot force-pushed the renovate/major-nextjs branch from 9547a5b to a0e34ed Compare January 15, 2024 10:39
@renovate renovate bot force-pushed the renovate/major-nextjs branch from a0e34ed to 79c7605 Compare January 18, 2024 23:25
Copy link
Contributor Author

renovate bot commented Jan 20, 2024

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

Warning: custom changes will be lost.

@sabertazimi sabertazimi force-pushed the renovate/major-nextjs branch from 16dcb05 to adcf41b Compare January 20, 2024 04:52

This PR has 34 quantified lines of changes. In general, a change size of upto 200 lines is ideal for the best PR experience!


Quantification details

Label      : Extra Small
Size       : +17 -17
Percentile : 13.6%

Total files changed: 4

Change summary by file extension:
.js : +16 -16
.json : +1 -1
.lock : +0 -0

Change counts above are quantified counts, based on the PullRequestQuantifier customizations.

Why proper sizing of changes matters

Optimal pull request sizes drive a better predictable PR flow as they strike a
balance between between PR complexity and PR review overhead. PRs within the
optimal size (typical small, or medium sized PRs) mean:

  • Fast and predictable releases to production:
    • Optimal size changes are more likely to be reviewed faster with fewer
      iterations.
    • Similarity in low PR complexity drives similar review times.
  • Review quality is likely higher as complexity is lower:
    • Bugs are more likely to be detected.
    • Code inconsistencies are more likely to be detected.
  • Knowledge sharing is improved within the participants:
    • Small portions can be assimilated better.
  • Better engineering practices are exercised:
    • Solving big problems by dividing them in well contained, smaller problems.
    • Exercising separation of concerns within the code changes.

What can I do to optimize my changes

  • Use the PullRequestQuantifier to quantify your PR accurately
    • Create a context profile for your repo using the context generator
    • Exclude files that are not necessary to be reviewed or do not increase the review complexity. Example: Autogenerated code, docs, project IDE setting files, binaries, etc. Check out the Excluded section from your prquantifier.yaml context profile.
    • Understand your typical change complexity, drive towards the desired complexity by adjusting the label mapping in your prquantifier.yaml context profile.
    • Only use the labels that matter to you, see context specification to customize your prquantifier.yaml context profile.
  • Change your engineering behaviors
    • For PRs that fall outside of the desired spectrum, review the details and check if:
      • Your PR could be split in smaller, self-contained PRs instead
      • Your PR only solves one particular issue. (For example, don't refactor and code new features in the same PR).

How to interpret the change counts in git diff output

  • One line was added: +1 -0
  • One line was deleted: +0 -1
  • One line was modified: +1 -1 (git diff doesn't know about modified, it will
    interpret that line like one addition plus one deletion)
  • Change percentiles: Change characteristics (addition, deletion, modification)
    of this PR in relation to all other PRs within the repository.


Was this comment helpful? 👍  :ok_hand:  :thumbsdown: (Email)
Customize PullRequestQuantifier for this repository.

@sabertazimi sabertazimi merged commit 729948e into main Jan 20, 2024
12 checks passed
@sabertazimi sabertazimi deleted the renovate/major-nextjs branch January 20, 2024 05:56
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Pull requests that update a dependency file Extra Small
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant