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

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
antd (source)	^5.11.2 -> ^5.11.4
typescript (source)	^5.2.2 -> ^5.3.2

---

Release Notes

ant-design/ant-design (antd)

v5.11.4

Compare Source

• 🐞 Fix where Image sets z-index abnormally in nested Modal. #​46035
• 🐞 Fix Button that disabled link button should not have navigate options when right click. #​46021
• Card
  • 🛠 Refactor the Card internal method getAction into a function component. #​46032
  • 🐞 Fix the problem of Card warning invalid annotation in Rollup. #​46024
• TypeScript
  • 🤖 Export the type definition for the required property of the Radio and Checkbox components. #​46028 @​nnmax

---

• 🐞 修复 Image 在嵌套 Modal 中设置 z-index 异常的问题。#​46035
• 🐞 修复 Button 禁用的链接按钮右键点击时会有打开新链接选项的问题。#​46021
• Card
  • 🛠 把 Card 内部方法 getAction 重构为函数组件。#​46032
  • 🐞 解决 Card 在 Rollup 中会警告 invalid annotation 的问题。#​46024
• TypeScript
  • 🤖 导出 Radio 和 Checkbox 组件的 required 属性的类型定义。#​46028 @​nnmax

v5.11.3

Compare Source

• 🐞 Fix Modal static method create zIndex too high will cover other popup content. #​46012
• Image
  • 🆕 Image preview support mobile touch interactive. #​45989 @​JarvisArt
  • 🐞 Fixed Image preview z-index conflict when in a nested pop-up. #​45979 @​kiner-tang
• 🐞 Fix Collapse header cursor style. #​45994
• 🐞 Fix ColorPicker not support Form disabled config. #​45978 @​RedJue
• 🐞 Fix Typography.Text ellipsis.tooltip cannot open under Layout component. #​45962
• 🐞 Remove Select native 🔍 icon from search input in Safari. #​46008
• 💄 Remove Rate useless style.#​45927 @​JarvisArt
• 🛠 UMD antd.js will try to reuse global @ant-design/cssinjs first now. #​46009
• 🌐 Improve eu_ES localization. #​45928 @​ionlizarazu

---

• 🐞 修复 Modal 静态方法创建 zIndex 过高会覆盖其他弹出内容的问题。#​46012
• Image
  • 🆕 Image 预览支持移动触摸事件交互。#​45989 @​JarvisArt
  • 🐞 修复 Image 预览在嵌套弹框中 z-index 设置不正确的问题。#​45979 @​kiner-tang
• 🐞 修复 Collapse 可折叠区域鼠标 hover 样式问题。#​45994
• 🐞 修复 ColorPicker 不支持 Form 组件的禁用问题。#​45978 @​RedJue
• 🐞 修复 Typography.Text code 在 Layout 下开启 ellipsis 时 tooltip 无效的问题。#​45962
• 🐞 修复 Select 搜索框在 Safari 下显示多余的 🔍 图标。#​46008
• 💄 删除 Rate 组件无用样式。 #​45927 @​JarvisArt
• 🛠 UMD 版本 antd.js 现在会优先使用全局的 @ant-design/cssinjs 依赖。#​46009
• 🌐 补充 eu_ES 国际化内容。#​45928 @​ionlizarazu

Microsoft/TypeScript (typescript)

v5.3.2: TypeScript 5.3

Compare Source

For release notes, check out the release announcement.

For the complete list of fixed issues, check out the

• fixed issues query for Typescript 5.3.0 (Beta).
• fixed issues query for Typescript 5.3.1 (RC).
• fixed issues query for Typescript 5.3.2 (Stable).

Downloads are available on:

• NuGet package

---

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.