fix: 限制 nette/utils 版本为稳定的 4.0 系列，避免安装 dev 或 RC 版本

[westng]

Summary by CodeRabbit

更新

• 维护
  • 更新了项目依赖库版本，以获取最新稳定版本中可能包含的性能改进和bug修复。

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[github-actions]

Hi, this is a READ-ONLY repository, please submit your PR on the https://github.com/mineadmin/components repository.

This Pull Request will close automatically.

Thanks!

[coderabbitai]

Caution

Review failed

The pull request is closed.

高层次总结

在 composer.json 中将 nette/utils 的依赖约束从 dev-master 版本更新为稳定的 4.0.* 版本，确保使用受支持的稳定发布版本。

变更

内聚体 / 文件	变更摘要
依赖版本更新 composer.json	将 nette/utils 依赖从 "dev-master" 更新为 "4.0.*"（稳定版本约束）

代码审查工作量估算

🎯 1 (微不足道) | ⏱️ ~3 分钟

需要特别关注的地方：

• 验证 nette/utils 4.0.* 版本与项目其他依赖的兼容性
• 确认迁移至稳定版本不会引入破坏性变更

诗歌

🐰 版本号跳跃，稳定向前行

dev-master 告别，4.0 来相迎

依赖约束明确，项目更安心

小兔欢欣跳跃，发布质量升

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment

---

📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between c335cc2 and 9946824.

📒 Files selected for processing (1)

• composer.json (1 hunks)

Tip

📝 Customizable high-level summaries are now available in beta!

You can now customize how CodeRabbit generates the high-level summary in your pull requests — including its content, structure, tone, and formatting.

• Provide your own instructions using the high_level_summary_instructions setting.
• Format the summary however you like (bullet lists, tables, multi-section layouts, contributor stats, etc.).
• Use high_level_summary_in_walkthrough to move the summary from the description to the walkthrough section.

Example instruction:

"Divide the high-level summary into five sections:

1. 📝 Description — Summarize the main change in 50–60 words, explaining what was done.
2. 📓 References — List relevant issues, discussions, documentation, or related PRs.
3. 📦 Dependencies & Requirements — Mention any new/updated dependencies, environment variable changes, or configuration updates.
4. 📊 Contributor Summary — Include a Markdown table showing contributions:
   | Contributor | Lines Added | Lines Removed | Files Changed |
5. ✔️ Additional Notes — Add any extra reviewer context.
   Keep each section concise (under 200 words) and use bullet or numbered lists for clarity."

Note: This feature is currently in beta for Pro-tier users, and pricing will be announced later.

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}