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

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
antd (source)	^4.20.2 -> ^4.20.4
webpack	^5.72.0 -> ^5.72.1
yarn	3.2.0 -> 3.2.1

---

Release Notes

ant-design/ant-design

v4.20.4

Compare Source

• 🐞 Fix broken List.Item type definition. #​35455 @​rsmeral
• 🐞 Fix Checkbox margin in Tree RTL mode. #​35491 @​miracles1919
• 🗑 Remove Cascader displayRender warning. #​35417 @​lalalazero

---

• 🐞 修复 List.Item 类型错误。#​35455 @​rsmeral
• 🐞 修复 Tree 组件 RTL 模式下 Checkbox 的间距。#​35491 @​miracles1919
• 🗑 删除 Cascader displayRender 警告。#​35417 @​lalalazero

v4.20.3

Compare Source

• 🐞 Fix unnecessary rowGap: 0 style attribute in Row. #​35409
• 🐞 Fix List.Item ref no work problem. #​35321
• 💄 Optimize the style of arrow in Tooltip. #​35401
• 🐞 Fix Table column filter reset is not working. #​35386 @​lalalazero
• 🌍 Add missing localizations for 🇬🇧 en_GB and 🇺🇦 uk_UA. #​35430 @​velykanov
• Typescript
  • 🤖 Fixed an issue where notification maxCount attribute was missing. #​35369 @​cwveysey

---

• 🔥 增加 官方国内镜像，享受飞一般的加载速度。
• 🐞 修复 Row 里不必要的 rowGap: 0 样式属性。#​35409
• 🐞 修复 List.Item ref 不生效的问题。#​35321
• 💄 优化 Tooltip 箭头的样式。#​35401
• 🐞 修复 Table 筛选的重置功能不生效问题。#​35386 @​lalalazero
• 🌍 为 🇬🇧 en_GB 和 🇺🇦 uk_UA 添加缺失的本地化文案。#​35430 @​velykanov
• TypeScript
  • 🤖 修复 Notification 的 maxCount 属性缺失的问题。#​35369 @​cwveysey

webpack/webpack

v5.72.1

Compare Source

Bugfixes

• fix __webpack_nonce__ with HMR
• fix in operator in some cases
• fix json parsing error messages
• fix module concatenation with using this.importModule
• upgrade enhanced-resolve

yarnpkg/berry

v3.2.1

Compare Source

Installs

• The pnpm linker no longer tries to remove node_modules directory, when node-modules linker is active
• The node-modules linker does not fail anymore if portal dependency points to an external project with multiple interdependent workspaces
• The node-modules linker has received various improvements:
  • applies hoisting algorithm on aliased dependencies
  • reinstalls modules that have their directories removed from node_modules by the user
  • improves portal hoisting
  • supports supportedArchitectures

Bugfixes

• The PnP ESM loader is now able to handle symlinked extensionless entrypoints.

---

Configuration

📅 Schedule: "every weekend" in timezone Asia/Shanghai.

🚦 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 WhiteSource Renovate. View repository job log here.

[pull-request-quantifier-deprecated]

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

Total files changed: 3

Change summary by file extension:
.yml : +1 -1
.json : +3 -3
.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.