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

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
antd (source)	^5.11.1 -> ^5.11.2
prettier (source)	^3.0.3 -> ^3.1.0
webpack-bundle-analyzer	^4.9.1 -> ^4.10.1
yarn	3.6.4 -> 3.7.0

---

Release Notes

ant-design/ant-design (antd)

v5.11.2

Compare Source

• 🆕 Table with virtual can now customize components except the components.body. #​45857
• 🐞 Fix Button with href and disabled that could be focused. #​45910 @​MadCcc
• 🐞 Fix zIndex logic problem that message and notification are covered when multiple Modal are opened. #​45911 #​45864 @​kiner-tang
• 💄 Fix QRCode style.padding is not working. #​45815
• 💄 Optimize Carousel dots border radius style. #​45817
• TypeScript
  • 🤖 Optimize List gutter property type definition. #​45791 @​Asanio06

---

• 🆕 放开 Table virtual 下 components 的限制，现在除了 components.body 都可以自定义。#​45857
• 🐞 修复 Button 带有链接且禁用时可以被聚焦到的问题。#​45910 @​MadCcc
• 🐞 修复 zIndex 逻辑，解决多层 Modal 打开时，message 与 notification 被遮盖的问题。#​45911 #​45864 @​kiner-tang
• 💄 修复 QRCode 设置 style.padding 时无效的问题。#​45815
• 💄 优化 Carousel 切换条圆角样式。#​45817
• TypeScript
  • 🤖 优化 List 属性 gutter 的类型定义。#​45791 @​Asanio06

prettier/prettier (prettier)

v3.1.0

Compare Source

diff

🔗 Release Notes

webpack-contrib/webpack-bundle-analyzer (webpack-bundle-analyzer)

v4.10.1

Compare Source

• Bug Fix
  • fix this.handleValueChange.cancel() is not a function (#​611 by @​life2015)

v4.10.0

Compare Source

• Improvement

  • Allows filtering the list of entrypoints (#​624 by @​chriskrogh)

• Internal

  • Make module much slimmer by replacing all lodash.* packages (#​612) by @​sukkaw.

yarnpkg/berry (yarn)

v3.7.0

Compare Source

---

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 10 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       : +5 -5
Percentile : 4%

Total files changed: 3

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