chore: Publish release/20250619-429588

[jackshen310]

Summary by CodeRabbit

• Chores
  • Updated package version to 1.3.1.
  • Added changelog entries for recent updates and bug fixes.
• Documentation
  • Updated changelog with details on new features and bug fixes.
• Revert
  • Removed obsolete metadata and changelog files related to previous changes.

[coderabbitai]

Walkthrough

This update removes several JSON metadata files documenting recent feature and patch changes to the @coze/api package and adds a new 1.3.1 changelog entry to both CHANGELOG.md and CHANGELOG.json. The package version is incremented from 1.3.0-beta.1 to 1.3.1 in package.json.

Changes

Files / Groups	Change Summary
common/changes/@coze/api/feat-*.json	Deleted JSON metadata files describing recent feature, refactor, and patch changes for @coze/api.
packages/coze-js/CHANGELOG.json packages/coze-js/CHANGELOG.md	Added changelog entries for version 1.3.1 summarizing new features and bug fixes.
packages/coze-js/package.json	Updated package version from 1.3.0-beta.1 to 1.3.1.

Possibly related PRs

• feat: refactor and fix aec bug on HarmonyOS #271: Deletes JSON changelog metadata files and documents the same refactor and bug fix for @coze/api as in this PR.

Suggested reviewers

• DingGao-Devin

Poem

In the warren of code, a version hops high,
Changelogs updated, old notes say goodbye.
Bugs are now patched, new features appear,
With 1.3.1, the future is clear!
🐇✨

— A rabbit, delighted, with ears in the sky

---

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.

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.

---

shenxiaojie.316 seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (1)

packages/coze-js/CHANGELOG.md (1)

3-4: Categorization of patch-level changes
Under “### Bug Fixes”, entries like “Publish feat/refactor” and “Publish feat/rtc-test” aren’t bug fixes. Consider introducing a “### Patches” or “### Maintenance” section for non-bugfix patch updates to improve clarity.

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 5fd4a7e and 5c1b83f.

📒 Files selected for processing (9)

• common/changes/@coze/api/feat-perf2_2025-06-16-13-08.json (0 hunks)
• common/changes/@coze/api/feat-refactor_2025-06-18-10-37.json (0 hunks)
• common/changes/@coze/api/feat-refactor_2025-06-18-10-53.json (0 hunks)
• common/changes/@coze/api/feat-refactor_2025-06-19-09-18.json (0 hunks)
• common/changes/@coze/api/feat-refactor_2025-06-19-09-26.json (0 hunks)
• common/changes/@coze/api/feat-rtc-test_2025-06-16-13-42.json (0 hunks)
• packages/coze-js/CHANGELOG.json (1 hunks)
• packages/coze-js/CHANGELOG.md (1 hunks)
• packages/coze-js/package.json (1 hunks)

💤 Files with no reviewable changes (6)

• common/changes/@coze/api/feat-perf2_2025-06-16-13-08.json
• common/changes/@coze/api/feat-refactor_2025-06-19-09-18.json
• common/changes/@coze/api/feat-refactor_2025-06-18-10-37.json
• common/changes/@coze/api/feat-refactor_2025-06-18-10-53.json
• common/changes/@coze/api/feat-refactor_2025-06-19-09-26.json
• common/changes/@coze/api/feat-rtc-test_2025-06-16-13-42.json

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

• GitHub Check: Node.js v20 (ubuntu-latest)
• GitHub Check: Analyze (javascript-typescript)

🔇 Additional comments (2)

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

3-3: Ensure git tag for new version
Make sure the corresponding git tag v1.3.1 is created and pushed to match this version bump.

packages/coze-js/CHANGELOG.json (1)

4-28: New changelog JSON entry is valid
The 1.3.1 record aligns with the Markdown changelog (version, timestamp, and comment groups). The entries are in descending order—no further changes needed here.