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

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
antd (source)	^4.22.4 -> ^4.22.6
webpack-bundle-analyzer	^4.5.0 -> ^4.6.0

---

Release Notes

ant-design/ant-design

v4.22.6

Compare Source

• 🐞 Revert #​36710 to fix Table onChange argument sorter error in multiple columns sort.
• 🐞 Fix Drawer can not close when config opacity on the maskStyle. #​37100

---

• 🐞 回滚 #​36710 以修复 Table 多列排序时 onChange 中 sorter 参数错误的问题。
• 🐞 修复 Drawer 的 maskStyle 配置 opacity 样式时无法关闭的问题。#​37100

v4.22.5

Compare Source

• 🇭🇺 Form add defaultValidateMessages.i18n az_AZ language #​23369. #​36967 @​YMiemie-cy
• 💄 Popover remove Popover incorrect box-shadow. #​37030 @​jerrykingxyz
• 🐞 Fix Steps tail position bug when labelPlacement="vertical". #​36996
• 💄 Removed exception error border for Pagination. #​36972 @​hydraZty
• 🐞 Fix Upload trigger mistake files status when upload multiple files at same time in React 18. #​36968
• TypeScript
  • 🤖 Fix type error of useWatch. #​37013 @​LiZhiHao97

---

• 🇭🇺 Form defaultValidateMessages.i18n 增加匈牙利语。#​36967 @​YMiemie-cy
• 💄 移除 Popover 中无效的 box-shadow 样式。#​37030 @​jerrykingxyz
• 🐞 修复 Steps labelPlacement="vertical" 时连接线位置偏上的问题。#​36996
• 💄 去掉 Pagination 的异常错误边框。#​36972 @​hydraZty
• 🐞 修复 Upload 在 React 18 下同时上传多份文件会出现上传状态不正确的问题。#​36968
• TypeScript
  • 🤖 修复 useWatch 的类型错误。#​37013 @​LiZhiHao97

webpack-contrib/webpack-bundle-analyzer

v4.6.0

Compare Source

• New Feature
  • Support outputting different URL in server mode (#​520 by @​southorange1228)
  • Use deterministic chunk colors (#501 by @​CreativeTechGuy)

---

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.

[pull-request-quantifier-deprecated]

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

Total files changed: 2

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