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

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
antd (source)	^5.12.2 -> ^5.12.5
html-webpack-plugin	^5.5.4 -> ^5.6.0

---

Release Notes

ant-design/ant-design (antd)

v5.12.5

Compare Source

• 💄 Fix Tabs style issue of editable mode when there is only "new" button left. #​46585 @​hzyhbk
• 💄 Fix Progress style issue of line mode with strokeLinecap. #​46551 @​ZN1996
• 🐞 Fix ColorPicker not support prefixCls. #​46561

---

• 💄 修复 Tabs 在 可编辑模式下只剩新增按钮时按钮的样式问题#​46585 @​hzyhbk
• 💄 修复 Progress strokeLinecap 不生效的问题。#​46551 @​ZN1996
• 🐞 修复 ColorPicker 配置 prefixCls 不生效的问题。#​46561

v5.12.4

Compare Source

• 🐞 Fix DatePicker style in cssVar mode. #​46526

---

• 🐞 修复 DatePicker 组件在 CSS 变量模式下的样式错乱问题。#​46526

v5.12.3

Compare Source

• 💄 修复 Tag 组件在 SSR 场景下的样式丢失问题。#​46500 @​MadCcc
• 🐞 Upload 的 disabled 属性不再对下载按钮生效。#​46454
• 💄 Upload.Dragger 增加一个水平内边距。#​46457
• 🐞 修复 Upload actions 的颜色问题。#​46456
• 🐞 修复 Form 使用 getValueProps 展示值无法更新的问题。#​46445
• 💄 修复 Checkbox 自定义 token.lineWidth 时勾选箭头错位问题。#​46431
• 🐞 修复 Select 组件定制 token 会让 padding 失效的问题。#​46427 @​MadCcc
• 🐞 修复 Message 在 cssVar 模式下覆盖组件 token 无效的问题。#​46415 @​MadCcc
• 💄 Flex 组件不应该应用额外的样式。#​46404 @​li-jia-nan

---

• 💄 Fix Tag that style would be missing in SSR. #​46500 @​MadCcc
• 🐞 Upload disabled prop should not affect download icon. #​46454
• 💄 Upload.Dragger add vertical padding style. #​46457
• 🐞 Fix Upload actions color issue. #​46456
• 🐞 Fix Form with getValueProps not working with value update. #​46445
• 💄 Fix Checkbox style when customize token.lineWidth. #​46431
• 🐞 Fix Select that custom token make padding broken. #​46427 @​MadCcc
• 🐞 Fix Message that token overrides not work in cssVar mode. #​46415 @​MadCcc
• 💄 Fix Flex component don't apply extra style. #​46404 @​li-jia-nan

jantimon/html-webpack-plugin (html-webpack-plugin)

v5.6.0

Compare Source

Features

• add @rspack/core as an optional peer dependency (#​1829) (56ff3ae)
• Added support type=systemjs-module via the scriptLoading option (#​1822) (7effc30)

Bug Fixes

• memory leak (#​1836) (c79f2cf)

5.5.4 (2023-12-06)

Bug Fixes

• avoid have undefined type for script tags (#​1809) (9959484)
• reemit assets from loaders (#​1811) (a214736)
• reemit favicon in serve/watch mode (#​1804) (57c5a4e)

5.5.3 (2023-06-10)

Bug Fixes

• don't add extra meta tag if it exists (#​1802) (8f92788)
• pass all Node.js globals to templates (#​1796) (f269fc0)
• types: fix type for chunkSortMode (#​1798) (6ad0e55)

5.5.2 (2023-06-08)

Bug Fixes

• compatibility with ES modules output (#​1795) (eda853b)

5.5.1 (2023-04-15)

Bug Fixes

• perf: defer loading of pretty-error to improve startup time (#​1789) (988709d)

---

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.