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 ^12.2.4 #951

Merged
merged 1 commit into from
Aug 5, 2022
Merged

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Aug 5, 2022

Mend Renovate

This PR contains the following updates:

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

Release Notes

vercel/next.js

v12.2.4

Compare Source

Core Changes
  • Fix error message typos: #​38894
  • Update to latest version of @​vercel/nft: #​38878
  • fix(#​38090): add missing analyticsId to config schema: #​38911
  • Ensure hash on initial request is preserved in new router: #​38913
  • Remove unnecessary assertions: #​38899
  • Clear unnecessary code: #​38900
  • fix: Impl attachRequestMeta in base server to handle meta differently in edge and node servers: #​38932
  • feat: enhance warning messages about unanalyzable config field: #​38907
  • fix: fix generateEtags type inside schema: #​38936
  • Refactor router reducer: #​38983
  • Add state comparison to router: #​38422
  • update webpack: #​38988
  • Update config schema for empty basePath: #​38998
  • Add handling for prefetching onTouchStart and initial mobile testing : #​38805
  • Add additional comments to new router: #​38986
  • Update config-schema for relay field to be less strict: #​39010
  • Add config for opting out of optimistic client cache behavior: #​38774
  • Fix tracing edge-runtime dependencies: #​39009
  • Ensure dangerouslyAllowSVG is passed correctly: #​39031
  • Handle getStaticPaths error inside worker to avoid serializing: #​39032
  • chore: enable swc externalHelpers when pre-compile: #​38182
  • Update to use HEAD request for On-Demand ISR: #​39038
  • chore: Clean up imports and unused code: #​39044
  • Replace node-sass test dependency with sass: #​39053
  • Add comments in new router reducer: #​39025
  • Add additional comments for reducer/cachenode: #​39065
  • fix: print Request & Response properties: #​38903
  • fix: show asPath on large page data warning: #​39071
  • Remove RSC rendering from render: #​39045
  • Ensure query is updated correctly with shallow and middleware: #​39086
  • Update pre-compiled to fix check: #​39089
  • Fix unhandled rejections with edge runtime: #​39091
  • feat(next-swc): Update swc: #​39055
  • Collect telemetry for next/future/image: #​39046
  • [Script] Adds onReady prop to next/script: #​38849
  • Ensure we hard navigate for failed _next/data with middleware: #​39148
  • Refactor Flight plugins to use types.: #​39136
  • Fix middleware + afterFiles SSG rewrite case: #​39153
  • Update swc minifier: #​39158
  • Fix incorrect component cache for middleware cases: #​39159
  • Add shared dynamic api: #​39163
  • Add exportPathMap config type/schema field: #​39171
  • Fix default error style overrides: #​39169
  • refactor: return single middleware from getMiddleware in dev server: #​39177
  • fix(#​11930): rewritten api routes can correctly handle cors in dev mode: #​38937
  • refactor: simplify middleware execution: #​39192
  • Add missing @​napi-rs/cli devDependency to next-swc: #​39164
  • Fix missing edge routes in dev middleware manifest: #​39199
  • Fix: only contain middleware in dev middleware manifest: #​39217
  • fix: react dev bundle is picked in prod mode: #​39221
  • Add "fill" mode to next/future/image: #​38855
  • Handle assetPrefix in app: #​39236
  • Export URLPattern from next/server: #​39219
  • Ensure middleware has single data fetch on query hydration with valid props: #​39210
  • Fix URLPattern next/server export on deploy: #​39290
  • Flush styles effects: #​39268
  • chore: rename typo middlewares to interceptors in hot reloader: #​39292
  • Remove default setting for object-fit on future fill images: #​39297
  • feat(config): implement a human readable ajv errors: #​39291
  • Enable concurrent mode by default in app-render: #​39307
  • Fix next/server being required during build: #​39310
  • feat(next-swc/wasm): export async interfaces: #​39231
  • Ensure On-Demand revalidate does not consider preview cookie: #​39313
  • fix: buffer is not usable on edge runtime: #​39227
Documentation Changes
  • Remove next-page-tester from testing.md: #​38920
  • Add section about building getStaticPaths on-demand.: #​38943
  • Docs: Fix grammatical typo: #​38962
  • docs: update typescript.md: #​38717
  • Add note to next/future/image about default styles.: #​38978
  • Add caveat note about shallow routing with middleware: #​39154
  • fix: Update testing.md: #​39195
  • Replaces getStaticProps with getStaticPaths: #​39218
  • Clear up rewrites documentation: #​39238
  • Add section about migrating from next/image to next/future/image: #​39270
  • [docs] Clarify polyfill support: #​39272
  • fix typo: docs/advanced-features/react-18/streaming.md: #​39293
  • docs: add missing dot: #​39314
Example Changes
  • Add example with cookies-next package: #​31243
  • chore(example): convert with-stitches to TS: #​38892
  • Update Convex example not to ignore generated files: #​38931
  • Convert custom-routes-proxying example to TypeScript: #​38974
  • Added workaround for --isolatedModules inside of configuration files: #​39004
  • Update default gitignore templates: #​39051
  • docs(examples): improve DX while copying command to create new project: #​38410
  • docs(example): Update Makeswift example: #​39070
  • fix: use if..elif..else in docker examples: #​39072
  • feat(with-mux-video): Update mux-player scope and version to latest.: #​39079
  • Convert cms-agilitycms example to TypeScript: #​38976
  • Convert the Cypress config to ESM Module syntax: #​39036
  • fix: missing semicolon on Dockerfile: #​39142
  • Fix typo in with-docker-compose README: #​39176
  • examples/with-msw-typescript: #​39196
  • Update edgedb.toml: #​39243
  • fix: use if...else in dockerfile: #​39263
  • Add TypeScript to ant design example: #​38470
Misc Changes
  • Update Safari 10 test to no longer wait for modern Safari: #​39028
  • Update delayed test output handling: #​39078
  • Update tests to use random directory: #​39230
  • Update Android NDK path for swc builds: #​39298
  • Add delay before exiting tests for log flushing: #​39302
  • chore(trace): fix typo in trace-to-event-format.mjs: #​39279
Credits

Huge thanks to @​theMosaad, @​SukkaW, @​timneutkens, @​Yuddomack, @​msquitieri, @​andreizanik, @​nix6839, @​shuding, @​thomasballinger, @​ziishaned, @​leerob, @​xyeres, @​nyedidikeke, @​maxproske, @​sokra, @​titusdmoore, @​thebergamo, @​fikrikarim, @​Kikobeats, @​balazsorban44, @​clearlyTHUYDOAN, @​ijjk, @​nasso, @​qutek, @​kdy1, @​kyliau, @​housseindjirdeh, @​huozhi, @​barissayil, @​seveibar, @​Jessidhia, @​santidalmasso, @​JohnDaly, @​Nikhilnama18, @​atcastle, @​styfle, @​Schniz, @​mduleone, @​colinhacks, @​ductnn, @​josh, @​hiro0218, @​eltociear, @​kwonoj, @​valcosmos, and @​feugy for helping!


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, click this checkbox.

This PR has been generated by Mend Renovate. View repository job log here.

@vercel
Copy link

vercel bot commented Aug 5, 2022

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

Name Status Preview Updated
blog ✅ Ready (Inspect) Visit Preview Aug 5, 2022 at 5:28PM (UTC)

@renovate renovate bot added the dependencies Pull requests that update a dependency file label Aug 5, 2022
@github-actions
Copy link
Contributor

github-actions bot commented Aug 5, 2022

Lighthouse Report

https://blog-38jtkyr0b-sabertaz.vercel.app/

🚀 Vercel preview deployment
Lighthouse report

Category Score
🟡 performance 89
🟢 accessibility 100
🟢 best-practices 100
🟢 seo 100
🟢 pwa 100

https://blog-38jtkyr0b-sabertaz.vercel.app/posts

🚀 Vercel preview deployment
Lighthouse report

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

https://blog-38jtkyr0b-sabertaz.vercel.app/tags

🚀 Vercel preview deployment
Lighthouse report

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

https://blog-38jtkyr0b-sabertaz.vercel.app/books

🚀 Vercel preview deployment
Lighthouse report

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

https://blog-38jtkyr0b-sabertaz.vercel.app/about

🚀 Vercel preview deployment
Lighthouse report

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

@codecov
Copy link

codecov bot commented Aug 5, 2022

Codecov Report

Merging #951 (62a8908) into main (47a4d84) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main     #951   +/-   ##
=======================================
  Coverage   99.42%   99.42%           
=======================================
  Files         176      176           
  Lines        1039     1039           
  Branches       88       88           
=======================================
  Hits         1033     1033           
  Misses          5        5           
  Partials        1        1           

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

@renovate renovate bot force-pushed the renovate/nextjs branch from dc4d533 to 62a8908 Compare August 5, 2022 17:24
@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
.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.

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