fix(deps): update dependencies (non-major)

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@codesandbox/sandpack-react	^1.2.2 -> ^1.2.4
@types/jest	^28.1.4 -> ^28.1.5
antd (source)	^4.21.5 -> ^4.21.6
eslint-config-next	^12.2.1 -> ^12.2.2
framer-motion	^6.4.3 -> ^6.5.0
jest (source)	^28.1.2 -> ^28.1.3
jest-environment-jsdom	^28.1.2 -> ^28.1.3
remark-github	^11.2.3 -> ^11.2.4
tailwindcss (source)	^3.1.5 -> ^3.1.6
ts-jest (source)	^28.0.5 -> ^28.0.6

---

Release Notes

codesandbox/sandpack

v1.2.4

Compare Source

Bug Fixes

• react: set react 18 as peer dependencies (#​529) (5a7e61c)

v1.2.3

Compare Source

Bug Fixes

• codemirror: use correct method to indent the code on tab key press (#​527) (6bea86b)

ant-design/ant-design

v4.21.6

Compare Source

• 🐞 Fix Skeleton active lost border-radius in Safari. #​36445
• 🐞 Fix Breadcrumb separators disappearing when used as last element in a List. #​36448 @​LeonKattendick
• 🐞 Fixed Upload removing file status color is wrong. #​36439
• 🐞 Fix DatePicker style issue when using status. #​35685 @​simplejason
• Table
  • 🐞 Fix Table scroll shadow style. #​36420 @​shunyue1320
  • 🐞 Fix Table hover render performance issue. #​36383
• 💄 Adjust Modal header close icon style. #​36309 @​cw1997
• 🐞 Fix Form.ErrorList shaking when validating too fast. #​36358
• 💄 Radio shadow color should be transparency to fit none-white background. #​36335
• 🐞 Fix Table border style issue when title configured. #​36384 @​Unuuuuu

---

• 🐞 修复 Skeleton 在 Safari 下开启 active 时圆角丢失的问题。#​36445
• 🐞 修复 Breadcrumb 作为 List 最后一个元素时，分割线丢失的问题。#​36448 @​LeonKattendick
• 🐞 修复 Upload 移除文件时状态色会变化的问题。#​36439
• 🐞 修复 DatePicker 配置 status 时的样式问题。#​35685 @​simplejason
• Table
  • 🐞 修复 Table 横向滚动的阴影样式问题。#​36420 @​shunyue1320
  • 🐞 修复 Table 鼠标悬浮时的性能问题。#​36383
• 💄 微调 Modal 标题上关闭按钮尺寸。#​36309 @​cw1997
• 🐞 修复 Form.ErrorList 在校验状态很快的时候视觉抖动问题。#​36358
• 💄 修复 Radio 聚焦时的阴影样式在非白底背景下的问题。#​36335
• 🐞 修复 Table 配置有 title 时的圆角样式。#​36384 @​Unuuuuu

vercel/next.js

v12.2.2

Compare Source

Core Changes

• Update README.md: #​38371
• Add support for catchall with new router: #​38439
• Fix client entry point prefix: #​38445
• Add support for optional catchall with new router: #​38444
• Add handling for back/forward (popstate) between old and new router: #​38453
• Make catchall parameters consistent with existing router: #​38456
• Fix warning next/future/image semicolon: #​38454
• fix(next/build): disable next-swc crash reporting temporarily: #​38472

Documentation Changes

• Update building-form sample code: #​38437
• Update i18n routing example with Middleware.: #​38419
• Adds mention of INP to "Measuring Performance" page: #​38464

Example Changes

• Replace JS blog-starter example with TS, deprecate blog-starter-typescript example: #​38395
• Convert api-routes-rate-limit example to TypeScript: #​38393
• examples(with-jotai): Update example: #​38398
• fix(examples/with-playwritght): use PORT env variable and fall back to 3000: #​38107
• docs: add trpc to examples: #​38272
• Convert api-routes-rest example to TypeScript: #​38394
• chore(examples): Convert api-routes-graphql example to TypeScript: #​38357

Credits

Huge thanks to @​mongolyy, @​balazsorban44, @​maxproske, @​leerob, @​huozhi, @​Thisen, @​thebergamo, @​zorrolisto, @​styfle, @​housseindjirdeh, and @​kwonoj for helping!

framer/motion

v6.5.0

Compare Source

Added

• useScroll for creating scroll-linked animations.

Deprecated

• useViewportScroll and useElementScroll.

facebook/jest

v28.1.3

Compare Source

Features

• [jest-leak-detector] Use native FinalizationRegistry when it exists to get rid of external C dependency (#​12973)

Fixes

• [jest-changed-files] Fix a lock-up after repeated invocations (#​12757)
• [@jest/expect-utils] Fix deep equality of ImmutableJS OrderedSets (#​12977)
• [jest-mock] Add index signature support for spyOn types (#​13013, #​13020)
• [jest-snapshot] Fix indentation of awaited inline snapshots (#​12986)

Chore & Maintenance

• [*] Replace internal usage of pretty-format/ConvertAnsi with jest-serializer-ansi-escapes (#​12935, #​13004)
• [docs] Update spyOn docs (#​13000)

remarkjs/remark-github

v11.2.4

Compare Source

• 792ad9c Fix to resolve package.jsons from file, not process
  by @​remcohaszing in https://github.com/remarkjs/remark-github/pull/41

Full Changelog: remarkjs/remark-github@11.2.3...11.2.4

tailwindlabs/tailwindcss

v3.1.6

Compare Source

Fixed

• Fix usage on Node 12.x (b4e637e)
• Handle theme keys with slashes when using theme() in CSS (#​8831)

kulshekhar/ts-jest

v28.0.6

Compare Source

Bug Fixes

• config: don't show diagnostics warning with diagnostics: false (#​3647) (9a9bc02), closes #​3638
• legacy: add useCaseSensitiveFileNames wherever needed (#​3683) (c40bc34), closes #​3665
• set @jest/types as peer dependency (#​3633) (24567e1)

---

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.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

---

• 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]

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

Name	Status	Preview	Updated
blog	✅ Ready (Inspect)	Visit Preview	Jul 14, 2022 at 7:50AM (UTC)

[github-actions]

Lighthouse Report

✨ https://blog-jo6bks88f-sabertaz.vercel.app/

🚀 Vercel preview deployment
⚡ Lighthouse report

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

✨ https://blog-jo6bks88f-sabertaz.vercel.app/posts

🚀 Vercel preview deployment
⚡ Lighthouse report

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

✨ https://blog-jo6bks88f-sabertaz.vercel.app/tags

🚀 Vercel preview deployment
⚡ Lighthouse report

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

✨ https://blog-jo6bks88f-sabertaz.vercel.app/books

🚀 Vercel preview deployment
⚡ Lighthouse report

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

✨ https://blog-jo6bks88f-sabertaz.vercel.app/about

🚀 Vercel preview deployment
⚡ Lighthouse report

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

[codecov]

Codecov Report

Merging #933 (10c19ec) into main (fbc38d2) will not change coverage.
The diff coverage is n/a.

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

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update fbc38d2...10c19ec. Read the comment docs.

[pull-request-quantifier-deprecated]

This PR has 20 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       : +10 -10
Percentile : 8%

Total files changed: 2

Change summary by file extension:
.json : +10 -10
.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 detetcted.
• 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.