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

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
antd (source)	^5.14.0 -> ^5.14.1
webpack	^5.90.1 -> ^5.90.2

---

Release Notes

ant-design/ant-design (antd)

v5.14.1

Compare Source

• 🐞 Fix Steps cannot interact correctly when type="inline". #​47406
• 🐞 Fix DatePicker & TimePicker arrow position not consider panel border radius distance. #​47389
• 🐞 Fix Dropdown should not display when items is empty array. #​47375
• 🐞 Fix Tag that should use defaultBg token with bordered={false}. #​47372 @​MadCcc
• 🐞 MISC: Fix that theme.inherit should not affect hashded and cssVar. #​47360 @​MadCcc
• 🐞 Fix Calendar panel not switch when change year or month. #​47361
• 💄 Fix Table's sub-table style issue in virtual mode. #​47333 @​Enigama

---

• 🐞 修复 Steps type="inline" 时鼠标无法 hover 到正确的步骤上的问题。#​47406
• 🐞 修复 DatePicker 与 TimePicker 弹出面板箭头没有考虑面板本身圆角的问题。#​47389
• 🐞 修复 Dropdown menu.items 为空时依然显示的问题。#​47375
• 🐞 修复 Tag 无边框模式没有正确使用 defaultBg 组件 token 的问题。#​47372 @​MadCcc
• 🐞 杂项：修复主题 inherit 配置会隔断 hashed 和 cssVar 配置的问题。#​47360 @​MadCcc
• 🐞 修复 Calendar 在切换年月时，面板没有跟着切换的问题。#​47361
• 💄 修复 Table 在虚拟模式下子表格的样式问题。#​47333 @​Enigama

webpack/webpack (webpack)

v5.90.2

Compare Source

Bug Fixes

• use Math.imul in fnv1a32 to avoid loss of precision, directly hash UTF16 values
• the setStatus() of the HMR module should not return an array, which may cause infinite recursion
• __webpack_exports_info__.xxx.canMangle shouldn't always same as default
• mangle export with destructuring
• use new runtime to reconsider skipped connections activeState
• make dynamic import optional in try/catch
• improve auto publicPath detection

Dependencies & Maintenance

• improve CI setup and include Node.js@21

---

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.