chore: update deps

[FliPPeDround]

Update dependencies

Summary by CodeRabbit

• Chores
  • Updated various dependency versions to ensure compatibility and access to the latest features and fixes, including updates to @skiyee/uni-ui, multiple @dcloudio packages, eslint, and @types/node. No changes to user-facing features or functionality.

[coderabbitai]

Walkthrough

This update consists solely of dependency version bumps across several package.json files within the project. No code, configuration, or script logic was altered. Only the versions of various dependencies and devDependencies were incremented to newer releases.

Changes

File(s)	Summary of Changes
packages/core/template/UI/skiyee/package.json	Updated @skiyee/uni-ui dependency from ^0.1.0 to ^0.1.1.
packages/core/template/base/package.json	Updated all @dcloudio dependencies and devDependencies from 3.0.0-4060620250520001 to 3.0.0-4070520250711001.
packages/core/template/config/lint/package.json	Updated eslint devDependency from ^9.30.1 to ^9.31.0.
packages/core/template/config/typescript/package.json	Updated @types/node devDependency from ^24.0.10 to ^24.0.13.

Possibly related PRs

• chore: update deps #40: Updates dependency versions in various package.json files within the template directories, including @dcloudio packages.
• chore: update deps #100: Performs similar dependency version bumps in multiple package.json files, indicating a continuation of version updates.
• chore: update deps #112: Updates several dependency versions in the same package.json files, but to earlier versions, showing sequential dependency management.

Poem

A hop and a skip, with versions anew,
Dependencies fresh as morning dew.
No code to refactor, no logic to bend,
Just numbers that climb and packages to mend.
With every update, the garden grows bright—
🐇 Cheers to version bumps done right!

---

📜 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 11b41a4 and 32961f7.

⛔ Files ignored due to path filters (1)

• pnpm-lock.yaml is excluded by !**/pnpm-lock.yaml

📒 Files selected for processing (4)

• packages/core/template/UI/skiyee/package.json (1 hunks)
• packages/core/template/base/package.json (1 hunks)
• packages/core/template/config/lint/package.json (1 hunks)
• packages/core/template/config/typescript/package.json (1 hunks)

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (6)

• GitHub Check: stable - x86_64-pc-windows-msvc - node@20
• GitHub Check: stable - aarch64-apple-darwin - node@20
• GitHub Check: stable - i686-pc-windows-msvc - node@20
• GitHub Check: stable - aarch64-pc-windows-msvc - node@20
• GitHub Check: stable - x86_64-apple-darwin - node@20
• GitHub Check: build (20.x, windows-latest)

🔇 Additional comments (4)

packages/core/template/UI/skiyee/package.json (1)

3-3: Dependency bump looks safe; don’t forget the lock-file.

Patch-level move from ^0.1.0 to ^0.1.1 for @skiyee/uni-ui is non-breaking.
Please make sure the workspace lock-file (pnpm-lock.yaml / package-lock.json) is regenerated and committed so CI runs against the exact new version.

packages/core/template/config/lint/package.json (1)

8-8: ESLint 9.31.0 may introduce new rule defaults—run the linter once.

Although this is a patch release, ESLint 9 is still rapidly evolving. Run pnpm run lint && pnpm run lint:fix locally to ensure no new warnings/errors are surfaced, and update the shared config if needed.

packages/core/template/config/typescript/package.json (1)

6-6: LGTM – type-definitions patch update.

@types/node moved from 24.0.10 → 24.0.13; no breaking changes expected.
Nothing else to flag.

packages/core/template/base/package.json (1)

44-60: Keep version parity across all Uni packages & ensure CLI match.

Good to see every @dcloudio/* package bumped to the unified tag 3.0.0-4070520250711001; avoids cross-version mismatches.

Action items:

1. Verify @dcloudio/types (still ^3.4.16) doesn’t require the same dated tag—CI compile will prove this.
2. Confirm the global/CLI install (uni, vite-plugin-uni) has been updated everywhere outside this template (e.g., root devDeps) to the same build to prevent runtime incompatibilities.
3. Regenerate and commit the root lock-file.

Everything else looks consistent.

Also applies to: 65-69

---

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

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Explain this complex logic.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai explain this code block.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and explain its main purpose.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR.
• @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.