chore: bump @rslib/core to 0.3.0

[fi3ework]

bump @rslib/core to 0.3.0, I manually reviewed the configuration and no breaking change is involved as far as I know.

Summary by CodeRabbit

• Chores
  • Updated @rslib/core dependency from version 0.0.18 to 0.3.0 in multiple packages
  • Dependency upgrade for @coze/api and @coze/realtime-api

[coderabbitai]

Walkthrough

This pull request involves updating the @rslib/core dependency version from 0.0.18 to 0.3.0 in two package.json files: one for the @coze/api package and another for the @coze/realtime-api package. The change appears to be a straightforward dependency version upgrade across multiple packages, potentially to incorporate recent improvements or bug fixes in the @rslib/core library.

Changes

File	Change Summary
packages/coze-js/package.json	Updated @rslib/core dependency version from 0.0.18 to 0.3.0
packages/realtime-api/package.json	Updated @rslib/core dependency version from 0.0.18 to 0.3.0

Possibly related PRs

• feat: use rslib to build esm cjs umd #27: Another PR involving updating the @rslib/core dependency version in package.json

Suggested reviewers

• Tecvan-fe

Poem

🐰 Hop, hop, version update time!
Dependencies dance in a new design
From 0.0.18 to 0.3.0 we climb
Library core gets a fresh paradigm
Coding rabbits rejoice with glee sublime! 🚀

---

📜 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 692145f and 325c649.

⛔ Files ignored due to path filters (1)

• common/config/subspaces/default/pnpm-lock.yaml is excluded by !**/pnpm-lock.yaml

📒 Files selected for processing (2)

• packages/coze-js/package.json (2 hunks)
• packages/realtime-api/package.json (2 hunks)

🔇 Additional comments (3)

packages/coze-js/package.json (2)

61-61: Consider moving @rslib/core to dependencies

Since this package relies on the rslib build system at runtime (via "rslib build" script), consider moving @rslib/core from devDependencies to dependencies.

Run this script to check if rslib is used only during build or also at runtime:

---

61-61: Verify breaking changes in @rslib/core 0.3.0

This is a significant version jump from 0.0.18 to 0.3.0. Since this package uses the rslib build system ("rslib build" in scripts), please ensure there are no breaking changes in the build configuration or API.

Run this script to check the changelog or release notes:

✅ Verification successful

@rslib/core upgrade appears safe

The version upgrade appears safe based on:

• Multiple packages in the monorepo are using @rslib/core 0.3.0 with identical build configurations
• Build configurations are simple and use standard features
• No version-specific workarounds or complex configurations are present

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Check for breaking changes in @rslib/core

# Search for CHANGELOG.md or similar files
fd -g 'CHANGELOG*' -g 'HISTORY*' -g 'RELEASES*'

# Search for breaking change indicators in commit messages
git log --oneline | rg -i "break|breaking|major"

Length of output: 201

---

Script:

#!/bin/bash
# Search for changelog files correctly
fd changelog -i

# Check package.json files for @rslib/core versions
rg "@rslib/core" -A 1 -B 1 "package.json$"

# Look for rslib usage patterns
rg "rslib" -A 2 -B 2

# Check build script usage
ast-grep --pattern 'rslib build'

Length of output: 5213

---

Script:

#!/bin/bash
# Read changelog content
cat packages/coze-js/CHANGELOG.md

# Check rslib config files for any version-specific configurations
cat packages/coze-js/rslib.config.ts
cat packages/realtime-api/rslib.config.ts

Length of output: 1703

packages/realtime-api/package.json (1)

60-60: Version consistency looks good

The @rslib/core version (0.3.0) is consistent with the version used in @coze/api package.

However, since this package depends on @coze/api as a workspace dependency, please ensure both packages are tested together to verify compatibility with the new @rslib/core version.

Run this script to check for potential version conflicts:

Finishing Touches

• 📝 Generate Docstrings

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ 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.
  • Generate unit testing code for this file.
  • 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 generate unit testing code for this file.
  • @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 generate unit testing code.
  • @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.

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. (Beta)
• @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.