chore: bump all (dev)Dependencies

[JounQin]

Summary by CodeRabbit

• Chores
  • Updated multiple development dependencies to newer versions. No changes to app functionality or user experience.

[changeset-bot]

🦋 Changeset detected

Latest commit: c867b21

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package

Name	Type
@alauda/doom	Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[coderabbitai]

Walkthrough

The changes introduce a new changeset file documenting a patch-level update for the @alauda/doom package and update several development dependencies in package.json to newer versions. No functional code changes or modifications to exported entities are included.

Changes

File(s)	Change Summary
.changeset/cyan-mails-type.md	Added a changeset file documenting a patch-level dev dependency bump
package.json	Updated multiple devDependencies to newer patch/minor versions

Poem

A bunny hops with cheerful might,
Updating tools to keep things light.
No code has changed, just versions new,
Dependencies fresh as morning dew.
With every patch, the garden grows—
Onward the project smoothly goes!
🐇✨

---

📜 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 e51390c and c867b21.

⛔ Files ignored due to path filters (1)

• yarn.lock is excluded by !**/yarn.lock, !**/*.lock

📒 Files selected for processing (2)

• .changeset/cyan-mails-type.md (1 hunks)
• package.json (3 hunks)

⏰ Context from checks skipped due to timeout of 90000ms (8)

• GitHub Check: Build and Lint with Node.js 22 on ubuntu-latest
• GitHub Check: Build and Lint with Node.js 20 on ubuntu-latest
• GitHub Check: Build and Lint with Node.js 24 on ubuntu-latest
• GitHub Check: Build and Lint with Node.js 18 on ubuntu-latest
• GitHub Check: Build and Lint with Node.js 24 on ubuntu-latest
• GitHub Check: Build and Lint with Node.js 20 on ubuntu-latest
• GitHub Check: Build and Lint with Node.js 22 on ubuntu-latest
• GitHub Check: Build and Lint with Node.js 18 on ubuntu-latest

🔇 Additional comments (3)

package.json (2)

59-61: Approve dependency version bumps

The updated dependencies (@cspell/eslint-plugin, @eslint-react/eslint-plugin, @inquirer/prompts, es-toolkit, eslint, tinyglobby, and typescript-eslint) have been bumped to newer patch or minor versions. These are non-breaking maintenance updates that keep the project up-to-date with security fixes and enhancements.

Also applies to: 72-73, 96-98

---

106-108: Approve devDependency version bumps

All listed devDependencies (@eslint/js, @swc/core, @types/node, @types/react, eslint-import-resolver-typescript, eslint-plugin-import-x) have been incremented to compatible patch/minor releases. No breaking changes are introduced, and it aligns with the chore objective of keeping tooling current.

Also applies to: 112-114, 119-120

.changeset/cyan-mails-type.md (1)

1-6: Approve changeset for patch-level chore

The changeset correctly documents a patch bump targeting only development dependencies, matching the updates in package.json. Ensure the CI release workflow picks up this changeset for a patch release.

---

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.

[Copilot]

Pull Request Overview

This pull request bumps various dependency and devDependency versions to keep the project up-to-date.

• Bumped versions for key libraries in production and development dependencies.
• Updated minor version increments that may require checking compatibility with existing configurations.

Comments suppressed due to low confidence (2)

package.json:112

• The upgrade in '@types/node' represents a significant version jump which might introduce breaking changes in Node APIs; please verify compatibility with the rest of the codebase.

"@types/node": "^22.15.24",

package.json:98

• Review the release notes for 'typescript-eslint' to ensure that the minor version update does not introduce changes that affect linting rules or configurations.

"typescript-eslint": "^8.33.0",

[pkg-pr-new]

Open in StackBlitz

npm i https://pkg.pr.new/@alauda/doom@38

commit: 76fff58