[Snyk] Upgrade next from 13.0.5 to 13.1.5

[snyk-bot]

Snyk has created this PR to upgrade next from 13.0.5 to 13.1.5.

ℹ️ Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.

---

• The recommended version is 49 versions ahead of your current version.
• The recommended version was released 21 days ago, on 2023-01-23.

Release notes

Package name: next

• 13.1.5 - 2023-01-23
  

  Core Changes

  • Revert "Revert "Initial support for metadata (#44729)"": #45113
  • Update incremental cache handler for minimal mode: #45123
  • build(cargo): update turbopack: #45126
  • Revert "Revert "Revert "Initial support for metadata (#44729)"" (#45113)": #45130
  • Update reducer comments: #45127
  • Ensure config warnings only show once: #45142
  • Don't log suppressed error during export: #45100
  • Add support for node: prefix when importing Node.js builtin modules: #45149

  Example Changes

  • update Mux Player to latest, pin to ^1 and pin upchunk to ^3 add Mux …: #45121

  Misc Changes

  • Update CODEOWNERS: #45178
  • Switch from yarn pack to pnpm pack in tests: #45167

  Credits

  Huge thanks to @ shuding, @ dylanjha, @ ijjk, @ Brooooooklyn, @ timneutkens, @ hanneslund, @ feedthejim, and @ JanKaifer for helping!

• 13.1.5-canary.3 - 2023-01-23
  

  Core Changes

  • Ensure config warnings only show once: #45142
  • Don't log suppressed error during export: #45100
  • Add support for node: prefix when importing Node.js builtin modules: #45149

  Misc Changes

  • Update CODEOWNERS: #45178
  • Switch from yarn pack to pnpm pack in tests: #45167

  Credits

  Huge thanks to @ hanneslund, @ timneutkens, @ feedthejim, and @ JanKaifer for helping!

• 13.1.5-canary.2 - 2023-01-22
  

  Core Changes

  • Update reducer comments: #45127

  Credits

  Huge thanks to @ timneutkens for helping!

• 13.1.5-canary.1 - 2023-01-21
  

  Core Changes

  • Revert "Revert "Revert "Initial support for metadata (#44729)"" (#45113)": #45130

  Credits

  Huge thanks to @ shuding for helping!

• 13.1.5-canary.0 - 2023-01-21
  

  Core Changes

  • Revert "Revert "Initial support for metadata (#44729)"": #45113
  • Update incremental cache handler for minimal mode: #45123
  • build(cargo): update turbopack: #45126

  Example Changes

  • update Mux Player to latest, pin to ^1 and pin upchunk to ^3 add Mux …: #45121

  Credits

  Huge thanks to @ shuding, @ dylanjha, @ ijjk, and @ Brooooooklyn for helping!

• 13.1.4 - 2023-01-20
  

  Core Changes

  • Initial support for metadata: #44729
  • Improve swc transforms: #45083
  • Update swc_core to v0.56.0: #44792
  • fix(#44077): allow edge runtime for api routes inside src/ folder: #45093
  • Revert "Initial support for metadata (#44729)": #45111
  • build(cargo): update turbopack: #45109

  Documentation Changes

  • Fix broken argument for rewrites on link reference docs: #45073
  • Cannot redeclare block-scoped variable 'cookie'.: #45079

  Misc Changes

  • Fix metadata e2e test on deploy: #45104
  • Update @ next/font/google data: #45092

  Credits

  Huge thanks to @ guilhermefront, @ shuding, @ kdy1, @ iamrobins, @ hanneslund, @ feugy, and @ jridgewell for helping!

• 13.1.4-canary.1 - 2023-01-20
  Read more
• 13.1.4-canary.0 - 2023-01-20
  Read more
• 13.1.3 - 2023-01-20
  Read more
• 13.1.3-canary.6 - 2023-01-20
  Read more
• 13.1.3-canary.5 - 2023-01-19
• 13.1.3-canary.4 - 2023-01-18
• 13.1.3-canary.3 - 2023-01-17
• 13.1.3-canary.2 - 2023-01-17
• 13.1.3-canary.1 - 2023-01-17
• 13.1.3-canary.0 - 2023-01-14
• 13.1.2 - 2023-01-12
• 13.1.2-canary.8 - 2023-01-12
• 13.1.2-canary.6 - 2023-01-12
• 13.1.2-canary.5 - 2023-01-12
• 13.1.2-canary.4 - 2023-01-10
• 13.1.2-canary.3 - 2023-01-09
• 13.1.2-canary.2 - 2023-01-06
• 13.1.2-canary.1 - 2023-01-05
• 13.1.2-canary.0 - 2023-01-04
• 13.1.1 - 2022-12-24
• 13.1.1-canary.1 - 2022-12-24
• 13.1.1-canary.0 - 2022-12-23
• 13.1.0 - 2022-12-22
• 13.0.8-canary.5 - 2022-12-22
• 13.0.8-canary.4 - 2022-12-22
• 13.0.8-canary.3 - 2022-12-21
• 13.0.8-canary.2 - 2022-12-20
• 13.0.8-canary.1 - 2022-12-20
• 13.0.8-canary.0 - 2022-12-15
• 13.0.7 - 2022-12-15
• 13.0.7-canary.7 - 2022-12-15
• 13.0.7-canary.6 - 2022-12-13
• 13.0.7-canary.5 - 2022-12-13
• 13.0.7-canary.4 - 2022-12-09
• 13.0.7-canary.3 - 2022-12-07
• 13.0.7-canary.1 - 2022-12-03
• 13.0.7-canary.0 - 2022-12-02
• 13.0.6 - 2022-12-02
• 13.0.6-canary.4 - 2022-12-02
• 13.0.6-canary.3 - 2022-12-01
• 13.0.6-canary.2 - 2022-11-29
• 13.0.6-canary.1 - 2022-11-25
• 13.0.6-canary.0 - 2022-11-24
• 13.0.5 - 2022-11-23

from next GitHub release notes

Commit messages

Package name: next

• 4e6ea4a v13.1.5
• 8dac22a v13.1.5-canary.3
• d356458 Switch from `yarn pack` to `pnpm pack` in tests (#45167)
• a5bfc5a Update CODEOWNERS (#45178)
• 9f9c9ea Add support for node: prefix when importing Node.js builtin modules (#45149)
• 1dcf981 Don't log suppressed error during export (#45100)
• 440560f Ensure config warnings only show once (#45142)
• 70282b7 v13.1.5-canary.2
• a8c3b71 Update reducer comments (#45127)
• ff50621 v13.1.5-canary.1
• b224c5f Revert "Revert "Revert "Initial support for metadata (#44729)"" (#45113)" (#45130)
• f970827 v13.1.5-canary.0
• 53be72b build(cargo): update turbopack (#45126)
• 2293438 Update incremental cache handler for minimal mode (#45123)
• 3659b5e update Mux Player to latest, pin to ^1 and pin upchunk to ^3 add Mux … (#45121)
• 259cbc1 Revert "Revert "Initial support for metadata (#44729)"" (#45113)
• 0a5d272 v13.1.4
• 3ce4789 v13.1.4-canary.1
• 6294e6a build(cargo): update turbopack (#45109)
• e0865b1 Revert "Initial support for metadata (#44729)" (#45111)
• e8ae4e2 fix(#44077): allow edge runtime for api routes inside src/ folder (#45093)
• 9db8145 Update swc_core to `v0.56.0` (#44792)
• d6b4c54 Update @ next/font/google data (#45092)
• dc119e2 Fix metadata e2e test on deploy (#45104)

Compare

---

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.

For more information:

🧐 View latest project report

🛠 Adjust upgrade PR settings

🔕 Ignore this dependency or unsubscribe from future upgrade PRs

[pull-request-quantifier-deprecated]

This PR has 2 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       : +1 -1
Percentile : 0.8%

Total files changed: 2

Change summary by file extension:
.json : +1 -1

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.