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

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
antd (source)	^5.9.1 -> ^5.9.2
autoprefixer	^10.4.15 -> ^10.4.16
postcss (source)	^8.4.29 -> ^8.4.30

---

⚠ Dependency Lookup Warnings ⚠

Warnings were logged while processing this repo. Please check the logs for more information.

---

Release Notes

ant-design/ant-design (antd)

v5.9.2

Compare Source

• 🐞 Fix Table selection column not align in center when size is small. #​44922
• 🐞 Fix Select style problem when label contains div element. #​44927
• 🐞 Fix Modal broken style of buttons when custom footer. #​44929 @​Wxh16144
• 🐞 Fix notification wrong pop-up animation when placement is bottom. #​44918 @​linxianxi
• 🐞 Fix missing inherited feedbackIcon in Form.Item with noStyle. #​44937

---

• 🐞 修复 Table small 尺寸时选择列没有居中对齐的问题。#​44922
• 🐞 修复 Select 当 label 内使用了 div 块级元素时的样式问题。#​44927
• 🐞 修复 Modal 自定义 footer 时按钮内容丢失的问题。#​44929 @​Wxh16144
• 🐞 修复 notification 底部弹出动画的问题。#​44918 @​linxianxi
• 🐞 修复 Form.Item 有 noStyle 属性时没有继承上下文的反馈图标的问题。#​44937

postcss/autoprefixer (autoprefixer)

v10.4.16

Compare Source

• Improved performance (by Romain Menke).
• Fixed docs (by Christian Oliff).

postcss/postcss (postcss)

v8.4.30

Compare Source

• Improved source map performance (by Romain Menke).

---

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 6 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       : +3 -3
Percentile : 2.4%

Total files changed: 2

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