chore: Publish release/20250703-6d64c9

[jackshen310]

Summary by CodeRabbit

• Bug Fixes

  • Resolved an issue where a ScriptProcessor was not correctly registered, preventing related errors.

• Chores

  • Updated version to 1.3.4.
  • Updated changelog to reflect the latest patch.

[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]

Walkthrough

This change removes two JSON metadata files related to a patch fix, and updates the changelog and version number for the @coze/api package. The changelog documents a bug fix addressing the "No ScriptProcessor was register with this name" issue. No source code or API changes are included.

Changes

Files	Change Summary
common/changes/@coze/api/fix-websocket_2025-07-02-01-45.json, common/changes/@coze/api/fix-websocket_2025-07-02-13-26.json	Deleted patch metadata files describing the ScriptProcessor registration fix.
packages/coze-js/CHANGELOG.json, packages/coze-js/CHANGELOG.md	Added changelog entries for version 1.3.4 documenting the ScriptProcessor registration bug fix.
packages/coze-js/package.json	Bumped version from 1.3.3 to 1.3.4.

Possibly related PRs

• fix(websocket): Fix No ScriptProcessor was register with this name #281: Documents and implements the same ScriptProcessor registration fix, with similar changelog and metadata updates.

Suggested reviewers

• DingGao-Devin

Poem

A patch hops in, so neat and small,
No more ScriptProcessor woes at all.
Changelogs grow, the version climbs,
Bugs are fixed in record time.
With every hop, the code feels right—
🐇✨ Release day’s pure delight!

---

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.

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (2)

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

7-7: Fix grammatical typo in the entry

was register → was registered for correct past-tense usage.

- - Fix No ScriptProcessor was register with this name
+ - Fix “No ScriptProcessor was registered with this name” error

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

11-12: Keep wording consistent with .md changelog

Mirror the corrected phrasing to avoid divergence between the two changelog formats.

-            "comment": "Fix No ScriptProcessor was register with this name"
+            "comment": "Fix “No ScriptProcessor was registered with this name” error"

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 59d889e and d69b469.

📒 Files selected for processing (5)

• common/changes/@coze/api/fix-websocket_2025-07-02-01-45.json (0 hunks)
• common/changes/@coze/api/fix-websocket_2025-07-02-13-26.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 (2)

• common/changes/@coze/api/fix-websocket_2025-07-02-13-26.json
• common/changes/@coze/api/fix-websocket_2025-07-02-01-45.json

🧰 Additional context used

🧠 Learnings (1)

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

Learnt from: huntye1
PR: coze-dev/coze-js#25
File: codecov.yml:4-8
Timestamp: 2024-11-12T09:27:06.509Z
Learning: In the `coze-js` project, when configuring `codecov.yml`, prefer using default settings initially for stability unless there's a specific need to change them.

🪛 LanguageTool

packages/coze-js/CHANGELOG.md

[uncategorized] ~7-~7: This verb may not be in the correct form. Consider using a different form for this context.
Context: ...Bug Fixes - Fix No ScriptProcessor was register with this name ## 1.3.3 - 2025-06-26 ...

(AI_EN_LECTOR_REPLACEMENT_VERB_FORM)

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

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

🔇 Additional comments (1)

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

3-3: Version bump validated – no stale @coze/api@1.3.3 references

No occurrences of the previous version were found in the workspace after running the grep check. This patch bump to 1.3.4 is ready to merge.