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

[Snyk] Upgrade next from 13.0.5 to 13.3.1 #284

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

snyk-bot
Copy link

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

ℹ️ 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 166 versions ahead of your current version.
  • The recommended version was released 23 days ago, on 2023-04-21.
Release notes
Package name: next
  • 13.3.1 - 2023-04-21
    Read more
  • 13.3.1-canary.19 - 2023-04-21

    Core Changes

    • fix snapshots broken by prettier (also fix .prettierignore): #48586
    • Reland app-router: new client-side cache semantics: #48685
    • Revert "Reland app-router: new client-side cache semantics": #48688

    Misc Changes

    • Add logs to release job: #48690

    Credits

    Huge thanks to @ ForsakenHarmony and @ huozhi for helping!

  • 13.3.1-canary.18 - 2023-04-21

    Core Changes

    • Add export runtime test for pages and fully remove experimental.runtime: #48630
    • Upgrade @ types/react to latest 18.x: #48645
    • app-router: new client-side cache semantics: #48383
    • Fix typo in fetchType annotation: #48646
    • Ensure latest React types for experimental release channel are used: #48641
    • Fix writeConfigurationDefaults.ts to correctly suggest changes in monorepos: #48668
    • Revert "app-router: new client-side cache semantics": #48678

    Example Changes

    • Update Mux example logo to new Mux brand: #48654

    Misc Changes

    • misc: fix flaky prefetch test: #48666
    • Re-add kodiak config: #48672

    Credits

    Huge thanks to @ huozhi, @ dylanjha, @ eps1lon, @ feedthejim, @ nabsul, @ shuding, and @ ijjk for helping!

  • 13.3.1-canary.17 - 2023-04-20

    Core Changes

    • Adding missing fields to the Manifest type: #48552
    • Add updated app dir cache handling: #48516
    • Upgrade React: #48589
    • use structured images with metainfo (blur placeholder): #48531
    • Land reverted fix for chunk file names: #48625
    • remove amp error in app dir: #48620
    • Add test case for #48583 and ignore hot-update scripts: #48587
    • Exclude app from _devPagesManifest.js in turbopack: #48633
    • replace defined values and add __NEXT_HAS_REWRITES define: #48628
    • implement /_next/image for local requests: #48622

    Documentation Changes

    • Docs: Unify note formatting: #48417
    • Fix TYPO in otel docs: #48623

    Misc Changes

    • Update start release flow: #48634
    • Fix version bump

    Credits

    Huge thanks to @ ryo-manba, @ Yovach, @ ijjk, @ timneutkens, @ sokra, @ jankaifer, @ shuding, @ huozhi, and @ ForsakenHarmony for helping!

  • 13.3.1-canary.16 - 2023-04-19

    Core Changes

    • build(cargo): move workspaces manifest to top level: #48198
    • Remove expired link resources via MutationObserver during development: #48578
    • prettier fix for next-swc: #47873
    • Fix chunk file names in flight manifest: #48583

    Documentation Changes

    • docs: fix minimum Node.js version to 14.18.0: #48545

    Credits

    Huge thanks to @ koba04, @ kwonoj, @ shuding, and @ ForsakenHarmony for helping!

  • 13.3.1-canary.15 - 2023-04-19

    Core Changes

    • Fix instrumentation.js initialization in prod on Vercel: #48557
    • Prefer to use deployment url for metadata routes on production: #48556
    • Fallback to deployment vercel url if metadataBase is not set on prod: #48570

    Credits

    Huge thanks to @ sophiebits and @ huozhi for helping!

  • 13.3.1-canary.14 - 2023-04-18

    Core Changes

    • feat(turbopack): support modularizeImports next.js config: #48511
    • refactor: move resolving metadata process into async Metadata component: #48536
    • Update history in useInsertionEffect: #48553

    Misc Changes

    Credits

    Huge thanks to @ kwonoj, @ jessewarren-aa, @ huozhi, and @ timneutkens for helping!

  • 13.3.1-canary.13 - 2023-04-18
    Read more
  • 13.3.1-canary.12 - 2023-04-18
  • 13.3.1-canary.11 - 2023-04-17
  • 13.3.1-canary.10 - 2023-04-17
  • 13.3.1-canary.9 - 2023-04-17
  • 13.3.1-canary.8 - 2023-04-15
  • 13.3.1-canary.7 - 2023-04-14
  • 13.3.1-canary.6 - 2023-04-13
  • 13.3.1-canary.5 - 2023-04-12
  • 13.3.1-canary.4 - 2023-04-10
  • 13.3.1-canary.3 - 2023-04-08
  • 13.3.1-canary.2 - 2023-04-07
  • 13.3.1-canary.1 - 2023-04-07
  • 13.3.1-canary.0 - 2023-04-07
  • 13.3.0 - 2023-04-06
  • 13.2.5-canary.34 - 2023-04-06
  • 13.2.5-canary.33 - 2023-04-06
  • 13.2.5-canary.32 - 2023-04-06
  • 13.2.5-canary.31 - 2023-04-05
  • 13.2.5-canary.30 - 2023-04-04
  • 13.2.5-canary.29 - 2023-04-04
  • 13.2.5-canary.28 - 2023-04-03
  • 13.2.5-canary.27 - 2023-04-02
  • 13.2.5-canary.26 - 2023-04-02
  • 13.2.5-canary.25 - 2023-04-01
  • 13.2.5-canary.24 - 2023-03-31
  • 13.2.5-canary.23 - 2023-03-31
  • 13.2.5-canary.22 - 2023-03-31
  • 13.2.5-canary.21 - 2023-03-30
  • 13.2.5-canary.20 - 2023-03-28
  • 13.2.5-canary.19 - 2023-03-27
  • 13.2.5-canary.18 - 2023-03-25
  • 13.2.5-canary.17 - 2023-03-25
  • 13.2.5-canary.16 - 2023-03-24
  • 13.2.5-canary.15 - 2023-03-23
  • 13.2.5-canary.14 - 2023-03-23
  • 13.2.5-canary.13 - 2023-03-22
  • 13.2.5-canary.12 - 2023-03-21
  • 13.2.5-canary.10 - 2023-03-21
  • 13.2.5-canary.9 - 2023-03-20
  • 13.2.5-canary.8 - 2023-03-17
  • 13.2.5-canary.7 - 2023-03-17
  • 13.2.5-canary.6 - 2023-03-17
  • 13.2.5-canary.5 - 2023-03-16
  • 13.2.5-canary.4 - 2023-03-15
  • 13.2.5-canary.3 - 2023-03-14
  • 13.2.5-canary.2 - 2023-03-13
  • 13.2.5-canary.1 - 2023-03-11
  • 13.2.5-canary.0 - 2023-03-10
  • 13.2.4 - 2023-03-10
  • 13.2.4-canary.9 - 2023-03-09
  • 13.2.4-canary.8 - 2023-03-09
  • 13.2.4-canary.7 - 2023-03-08
  • 13.2.4-canary.6 - 2023-03-07
  • 13.2.4-canary.5 - 2023-03-07
  • 13.2.4-canary.4 - 2023-03-05
  • 13.2.4-canary.3 - 2023-03-04
  • 13.2.4-canary.2 - 2023-03-04
  • 13.2.4-canary.1 - 2023-03-03
  • 13.2.4-canary.0 - 2023-03-02
  • 13.2.3 - 2023-03-01
  • 13.2.3-canary.1 - 2023-03-01
  • 13.2.3-canary.0 - 2023-03-01
  • 13.2.2 - 2023-03-01
  • 13.2.2-canary.5 - 2023-03-01
  • 13.2.2-canary.4 - 2023-02-28
  • 13.2.2-canary.3 - 2023-02-28
  • 13.2.2-canary.2 - 2023-02-28
  • 13.2.2-canary.1 - 2023-02-25
  • 13.2.2-canary.0 - 2023-02-25
  • 13.2.1 - 2023-02-24
  • 13.2.1-canary.0 - 2023-02-24
  • 13.2.0 - 2023-02-23
  • 13.1.7-canary.32 - 2023-02-23
  • 13.1.7-canary.30 - 2023-02-23
  • 13.1.7-canary.29 - 2023-02-23
  • 13.1.7-canary.28 - 2023-02-23
  • 13.1.7-canary.27 - 2023-02-22
  • 13.1.7-canary.26 - 2023-02-22
  • 13.1.7-canary.25 - 2023-02-22
  • 13.1.7-canary.24 - 2023-02-22
  • 13.1.7-canary.23 - 2023-02-22
  • 13.1.7-canary.22 - 2023-02-21
  • 13.1.7-canary.21 - 2023-02-18
  • 13.1.7-canary.20 - 2023-02-18
  • 13.1.7-canary.19 - 2023-02-18
  • 13.1.7-canary.18 - 2023-02-17
  • 13.1.7-canary.17 - 2023-02-17
  • 13.1.7-canary.16 - 2023-02-16
  • 13.1.7-canary.15 - 2023-02-15
  • 13.1.7-canary.14 - 2023-02-15
  • 13.1.7-canary.13 - 2023-02-14
  • 13.1.7-canary.12 - 2023-02-14
  • 13.1.7-canary.11 - 2023-02-13
  • 13.1.7-canary.10 - 2023-02-11
  • 13.1.7-canary.9 - 2023-02-11
  • 13.1.7-canary.8 - 2023-02-09
  • 13.1.7-canary.7 - 2023-02-07
  • 13.1.7-canary.6 - 2023-02-06
  • 13.1.7-canary.5 - 2023-02-04
  • 13.1.7-canary.4 - 2023-02-02
  • 13.1.7-canary.3 - 2023-02-02
  • 13.1.7-canary.2 - 2023-02-01
  • 13.1.7-canary.1 - 2023-01-31
  • 13.1.7-canary.0 - 2023-01-31
  • 13.1.6 - 2023-01-28
  • 13.1.6-canary.3 - 2023-01-28
  • 13.1.6-canary.2 - 2023-01-27
  • 13.1.6-canary.1 - 2023-01-25
  • 13.1.6-canary.0 - 2023-01-23
  • 13.1.5 - 2023-01-23
  • 13.1.5-canary.3 - 2023-01-23
  • 13.1.5-canary.2 - 2023-01-22
  • 13.1.5-canary.1 - 2023-01-21
  • 13.1.5-canary.0 - 2023-01-21
  • 13.1.4 - 2023-01-20
  • 13.1.4-canary.1 - 2023-01-20
  • 13.1.4-canary.0 - 2023-01-20
  • 13.1.3 - 2023-01-20
  • 13.1.3-canary.6 - 2023-01-20
  • 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
  • 6423285 v13.3.1
  • 9314fb6 Wait for versioning prompt to show up for stable release (#48692)
  • 455de08 v13.3.1-canary.19
  • 4f1b0f7 Add logs to release job (#48690)
  • 8089d0a Revert "Reland app-router: new client-side cache semantics" (#48688)
  • b61305a Reland app-router: new client-side cache semantics (#48685)
  • 4354eda fix snapshots broken by prettier (also fix .prettierignore) (#48586)
  • a06fef0 v13.3.1-canary.18
  • 52fcc59 Revert "app-router: new client-side cache semantics" (#48678)
  • f779f10 Re-add kodiak config (#48672)
  • 8fd9a39 Fix writeConfigurationDefaults.ts to correctly suggest changes in monorepos (#48668)
  • abbf352 misc: fix flaky prefetch test (#48666)
  • 680564c Ensure latest React types for experimental release channel are used (#48641)
  • 8050a6c Fix typo in fetchType annotation (#48646)
  • 658c600 app-router: new client-side cache semantics (#48383)
  • db00867 Upgrade `@ types/react` to latest 18.x (#48645)
  • e952160 Update Mux example logo to new Mux brand (#48654)
  • cc684d0 Add export runtime test for pages and fully remove experimental.runtime (#48630)
  • 682fb27 v13.3.1-canary.17
  • 652ba8a Fix version bump
  • a7b0ae3 implement /_next/image for local requests (#48622)
  • ec385de replace defined values and add `__NEXT_HAS_REWRITES` define (#48628)
  • 8ab6c4c Exclude app from `_devPagesManifest.js` in turbopack (#48633)
  • 3a83c6b Update start release flow (#48634)

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant