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

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
antd (source)	^5.2.0 -> ^5.2.1
webpack-bundle-analyzer	^4.7.0 -> ^4.8.0

---

Release Notes

ant-design/ant-design

v5.2.1

Compare Source

• 🛠 Rewrite panelRender in Tour to funtion component。#​40670 @​li-jia-nan
• 🐞 Fix className property wrongly passed to child nodes in TimeLine。#​40700 @​any1024
• 🐞 Fix Silder dot to trigger click and hover correctly. #​40679 @​LongHaoo
• 🐞 Fix Tour that should support 0 as element. #​40631 @​li-jia-nan
• 💄 Fix DataPicker.RangePicker hover range style. #​40607 @​Yuiai01
• 💄 Optimize Steps custom icon size. #​40672 @​MadCcc
• TypeScript
  • 🤖 Update Upload to support generic types. #​40634 @​riyadelberkawy
• 🌐 Localization
  • 🇷🇺/🇺🇦 add missing translations for ru_RU and uk_UA. #​40656 @​eldarcodes

---

• 🛠 重构 Tour 中 panelRender 为函数式组件。#​40670 @​li-jia-nan
• 🐞 修复 TimeLine 中 className 传给子节点的问题。#​40700 @​any1024
• 🐞 修复 Silder 中的标记点在边缘无法点击的问题。#​40679 @​LongHaoo
• 🐞 修复 Tour 不支持 0 作为节点的问题。#​40631 @​li-jia-nan
• 💄 修复 DataPicker.RangePicker 的 hover 范围样式。#​40607 @​Yuiai01
• 💄 优化 Steps 组件自定义 icon 的大小。#​40672 @​MadCcc
• TypeScript
  • 🤖 Upload 组件支持泛型。#​40634 @​riyadelberkawy
• 🌐 国际化
  • 🇷🇺/🇺🇦 补全 ru_RU 和 uk_UA 文案。#​40656 @​eldarcodes

webpack-contrib/webpack-bundle-analyzer

v4.8.0

Compare Source

• Improvement

  • Support reading large (>500MB) stats.json files (#​423 by @​henry-alakazhang)
  • Improve search UX by graying out non-matches (#​554 by @​starpit)

• Internal

  • Add Node.js v16.x to CI and update GitHub actions (#​539 by @​amareshsm)

---

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, check this box

---

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.