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

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
antd (source)	^4.21.5 -> ^4.21.6
postcss-loader	^7.0.0 -> ^7.0.1

---

Release Notes

ant-design/ant-design

v4.21.6

Compare Source

• 🐞 Fix Skeleton active lost border-radius in Safari. #​36445
• 🐞 Fix Breadcrumb separators disappearing when used as last element in a List. #​36448 @​LeonKattendick
• 🐞 Fixed Upload removing file status color is wrong. #​36439
• 🐞 Fix DatePicker style issue when using status. #​35685 @​simplejason
• Table
  • 🐞 Fix Table scroll shadow style. #​36420 @​shunyue1320
  • 🐞 Fix Table hover render performance issue. #​36383
• 💄 Adjust Modal header close icon style. #​36309 @​cw1997
• 🐞 Fix Form.ErrorList shaking when validating too fast. #​36358
• 💄 Radio shadow color should be transparency to fit none-white background. #​36335
• 🐞 Fix Table border style issue when title configured. #​36384 @​Unuuuuu

---

• 🐞 修复 Skeleton 在 Safari 下开启 active 时圆角丢失的问题。#​36445
• 🐞 修复 Breadcrumb 作为 List 最后一个元素时，分割线丢失的问题。#​36448 @​LeonKattendick
• 🐞 修复 Upload 移除文件时状态色会变化的问题。#​36439
• 🐞 修复 DatePicker 配置 status 时的样式问题。#​35685 @​simplejason
• Table
  • 🐞 修复 Table 横向滚动的阴影样式问题。#​36420 @​shunyue1320
  • 🐞 修复 Table 鼠标悬浮时的性能问题。#​36383
• 💄 微调 Modal 标题上关闭按钮尺寸。#​36309 @​cw1997
• 🐞 修复 Form.ErrorList 在校验状态很快的时候视觉抖动问题。#​36358
• 💄 修复 Radio 聚焦时的阴影样式在非白底背景下的问题。#​36335
• 🐞 修复 Table 配置有 title 时的圆角样式。#​36384 @​Unuuuuu

webpack-contrib/postcss-loader

v7.0.1

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, click this checkbox.

---

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 detetcted.
• 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.