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

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
antd (source)	^5.13.0 -> ^5.13.2
autoprefixer	^10.4.16 -> ^10.4.17
commit-and-tag-version	^12.1.0 -> ^12.2.0
css-loader	^6.9.0 -> ^6.9.1
prettier (source)	^3.2.2 -> ^3.2.4
stylelint (source)	^16.1.0 -> ^16.2.0

---

Release Notes

ant-design/ant-design (antd)

v5.13.2

Compare Source

• 🐞 Fix that the inline rendering does not take effect when the preview.getContainer value for Image is false. #​47034 @​FEyudong
• 🐞 Fix Modal static function with prefixCls breaks children other component prefixCls and thus bring the motion miss. #​47010
• 🐞 Fix ok button of the DatePicker becomes compacted when used with Space.Compact. #​46769 @​Fatpandac
• 💄 Optimize Tree draggable node cursor style and collaspe icon hover style. #​46974

---

• 🐞 修复 Image 组件 preview.getContainer 值为 false 时，内联渲染不生效的问题。#​47034 @​FEyudong
• 🐞 修复 Modal 静态方法配置 prefixCls 时，会改变所有子元素的 prefixCls 并导致动画丢失的问题。#​47010
• 🐞 修复 Space.Compact 与 DatePicker 一起使用导致 DatePicker 的确认按钮样式错误。#​46769 @​Fatpandac
• 💄 优化 Tree 拖拽节点和展开收起按钮的鼠标 hover 样式。#​46974

v5.13.1

Compare Source

• 🐞 Fix Checkbox type error with @types/react version 16 or 17. #​46962 @​crazyair

---

• 🐞 修复 Checkbox 组件在 @types/react 16 或 17 版本下 Typescript 报错。#​46962 @​crazyair

postcss/autoprefixer (autoprefixer)

v10.4.17

Compare Source

• Fixed user-select: contain prefixes.

absolute-version/commit-and-tag-version (commit-and-tag-version)

v12.2.0

Compare Source

Features

• updater: add maven pom.xml file support (#​33, #​109) (#​123) (6466beb)

webpack-contrib/css-loader (css-loader)

v6.9.1

Compare Source

prettier/prettier (prettier)

v3.2.4

Compare Source

diff

Fix incorrect parser inference (#​15947 by @​fisker)

Files like .eslintrc.json were incorrectly formatted as JSONC files.

// Input
prettier --file-info .eslintrc.json
{ "ignored": false, "inferredParser": "jsonc" }

// Prettier 3.2.4
prettier --file-info .eslintrc.json
{ "ignored": false, "inferredParser": "json" }

v3.2.3

Compare Source

diff

Throw errors for invalid code (#​15881 by @​fisker, @​Josh-Cena, @​auvred)

// Input
1++;

// Prettier 3.2.2
1++;

// Prettier 3.2.3
SyntaxError: Invalid left-hand side expression in unary operation (1:1)
> 1 | 1++;
    | ^

// Input
try {} catch (error = 1){}

// Prettier 3.2.2
try {
} catch (error) {}

// Prettier 3.2.3
SyntaxError: Catch clause variable cannot have an initializer. (1:23)
> 1 | try {} catch (error = 1){}
    |                       ^

Fix parser inference (#​15927 by @​fisker)

// Prettier 3.2.2
prettier --file-info tsconfig.json
{ "ignored": false, "inferredParser": "json" }

// Prettier 3.2.3
prettier --file-info tsconfig.json
{ "ignored": false, "inferredParser": "jsonc" }

stylelint/stylelint (stylelint)

v16.2.0

Compare Source

• Added: media-query-no-invalid specific problem messages (#​7462) (@​romainmenke).
• Added: checkContextFunctionalPseudoClasses: [] to selector-max-id (#​7380) (@​brigitamaria).
• Fixed: declaration-property-value-no-unknown false negatives for @starting-style (#​7461) (@​fpetrakov).
• Fixed: function-no-unknown|value-keyword-case false positives for template literals with line breaks (#​7443) (@​Sh031224).
• Fixed: allowEmptyInput option ignored in configuration object regression (#​7446) (@​ybiquitous).
• Fixed: at-rule-no-unknown false positives for @starting-style (#​7438) (@​fpetrakov).
• Fixed: ERR_UNSUPPORTED_ESM_URL_SCHEME for --custom-formatter on Windows (#​7432) (@​JounQin).
• Fixed: Error: Could not find <package> message clarity (#​7456) (@​jeddy3).
• Fixed: overrides.files negated pattern regression introduced in 15.0.0 (#​7468) (@​ybiquitous).

---

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: 2

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