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

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
antd (source)	^5.8.3 -> ^5.8.4
postcss (source)	^8.4.27 -> ^8.4.28
prettier (source)	^3.0.1 -> ^3.0.2
stylelint (source)	^15.10.2 -> ^15.10.3
yarn	3.6.1 -> 3.6.2

---

Release Notes

ant-design/ant-design (antd)

v5.8.4

Compare Source

• ColorPicker
  • 🐞 Fix the cursor jumps when entering lowercase English letters in the ColorPicker color value input box. #​44137 @​gouge666
  • 🐞 Fix the ColorPicker style is deformed under different sizes. #​44273 @​kouchao
• 🐞 Fix Descriptions throwing key is not a prop error message. #​44278 @​RedJue
• 🐞 Fix the node is still rendered when Pagination itemRender is customized to null. #​44226
• 🐞 Fix Modal in Dropdown menu.items, rapid mouse movement when expanding Modal will make Dropdown reopen. #​44204
• DatePicker
  • 💄 Fix DatePicker content is not centered. #​44245 @​Zian502
  • 💄 Optimize DatePicker selection range style. #​44206 @​kiner-tang
• 💄 Fix clicking on the Tabs area on the mobile terminal triggers a color change. #​44200 @​yilaikesi
• RTL
  • 💄 Fix the numbers in the Badge are also RTL when the text direction of the page is RTL. #​43998 @​NotEvenANeko

---

• ColorPicker
  • 🐞 修复 ColorPicker 色值输入框输入小写英文字母时光标跳动的问题。#​44137 @​gouge666
  • 🐞 修复 ColorPicker 在不同尺寸下样式变形的问题。#​44273 @​kouchao
• 🐞 修复 Descriptions 抛出 key is not a prop 的错误提示。#​44278 @​RedJue
• 🐞 修复 Pagination itemRender 自定义为 null 时，仍然渲染节点的问题。#​44226
• 🐞 修复 Modal 在 Dropdown menu.items 中，展开 Modal 时快速移动鼠标会使 Dropdown 重新打开的问题。#​44204
• DatePicker
  • 💄 修复 DatePicker 内容不居中问题。#​44245 @​Zian502
  • 💄 优化 DatePicker 中范围选择区域样式。#​44206 @​kiner-tang
• 💄 修复移动端点击 Tabs 区域触发颜色改变的问题。#​44200 @​yilaikesi
• RTL
  • 💄 修复了当页面的文字方向为 RTL 时 Badge 里面的数字也是 RTL 的问题。#​43998 @​NotEvenANeko

postcss/postcss (postcss)

v8.4.28

Compare Source

• Fixed Root.source.end for better source map (by Romain Menke).
• Fixed Result.root types when process() has no parser.

prettier/prettier (prettier)

v3.0.2

Compare Source

diff

Break after = of assignment if RHS is poorly breakable AwaitExpression or YieldExpression (#​15204 by @​seiyab)

// Input
const { section, rubric, authors, tags } = await utils.upsertCommonData(mainData);

// Prettier 3.0.1
const { section, rubric, authors, tags } = await utils.upsertCommonData(
  mainData,
);

// Prettier 3.0.2
const { section, rubric, authors, tags } =
  await utils.upsertCommonData(mainData);

Do not add trailing comma for grouped scss comments (#​15217 by @​auvred)

/* Input */
$foo: (
	'property': (),
	// comment 1
	// comment 2
)

/* Prettier 3.0.1 */
$foo: (
  "property": (),
  // comment 1
  // comment 2,
);

/* Prettier 3.0.2 */
$foo: (
  "property": (),
  // comment 1
  // comment 2
);

Print declare and export keywords for nested namespace (#​15249 by @​sosukesuzuki)

// Input
declare namespace abc1.def {}
export namespace abc2.def {}

// Prettier 3.0.1
namespace abc1.def {}
namespace abc2.def {}

// Prettier 3.0.2
declare namespace abc1.def {}
export namespace abc2.def {}

stylelint/stylelint (stylelint)

v15.10.3

Compare Source

• Fixed: declaration-property-value-no-unknown false negatives for typed custom properties (#​7078) (@​romainmenke).
• Fixed: property-no-unknown false positives for scroll-driven animations (#​7090) (@​renato-bohler).

yarnpkg/berry (yarn)

v3.6.2

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 12 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       : +6 -6
Percentile : 4.8%

Total files changed: 3

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

[socket-security]

Removed dependencies detected. Learn more about Socket for GitHub ↗︎

🚮 Removed packages: stylelint@15.10.2