chore: Publish release/20250708-8acb90#284
Conversation
|
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. |
WalkthroughThis change updates the version numbers and changelogs for the Changes
Possibly related PRs
Suggested reviewers
Poem
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. 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
SupportNeed 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)
Other keywords and placeholders
CodeRabbit Configuration File (
|
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 1
🧹 Nitpick comments (2)
packages/coze-js/CHANGELOG.md (1)
3-8: Changelog entry is too vague“Publish for noop” provides no actionable context.
At minimum specify why a new patch was required (e.g., republish due to broken tarball, metadata fix). Clear changelogs help downstream maintainers decide on upgrades.packages/coze-uniapp/CHANGELOG.md (1)
3-8: Consistent casing of “WebSocket”Elsewhere in docs you use the proper “WebSocket”.
Keep terminology consistent:- - fix Websocket undefined + - fix WebSocket undefined
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (7)
common/changes/@coze/uniapp-api/fix-uniappbug_2025-07-06-13-31.json(0 hunks)packages/coze-js/CHANGELOG.json(1 hunks)packages/coze-js/CHANGELOG.md(1 hunks)packages/coze-js/package.json(1 hunks)packages/coze-uniapp/CHANGELOG.json(1 hunks)packages/coze-uniapp/CHANGELOG.md(1 hunks)packages/coze-uniapp/package.json(1 hunks)
💤 Files with no reviewable changes (1)
- common/changes/@coze/uniapp-api/fix-uniappbug_2025-07-06-13-31.json
🧰 Additional context used
🧠 Learnings (4)
packages/coze-uniapp/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.
packages/coze-js/CHANGELOG.md (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.
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.
packages/coze-js/CHANGELOG.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.
⏰ 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). (2)
- GitHub Check: Node.js v20 (ubuntu-latest)
- GitHub Check: Analyze (javascript-typescript)
🔇 Additional comments (4)
packages/coze-uniapp/package.json (2)
3-3: Missing lock-file update may break reproducible installsThe package version bumps to
0.3.1, but no accompanying lock-file (pnpm-lock.yaml,package-lock.json, etc.) is committed in this PR.
If the workspace is published from CI that installs from a clean clone, the lock file is required for deterministic dependency resolution—especially because you rely onworkspace:*links.Consider committing the updated lock-file or explicitly documenting why it is omitted (e.g., lock-files are generated in CI).
68-71: Overly strict peerDependency pin risks install conflicts
"@dcloudio/uni-app": "3.0.0-4030620241128001"is a pre-release build pinned to an exact version.
Consumers on a later 3.x build will hit an npm/yarn/ pnpm peer‐resolution error.Unless you rely on that exact build, relax the range:
- "@dcloudio/uni-app": "3.0.0-4030620241128001" + "@dcloudio/uni-app": "^3.0.0"[ suggest_essential_refactor ]
packages/coze-js/package.json (1)
3-3: Patch release without code changes — double-check necessityVersion bumps increase maintenance overhead for consumers who track
^1.3.x.
Given the changelog entry “Publish for noop”, verify that:
- No generated artifacts (e.g.,
dist) changed.- No transitive dependency resolutions differ.
If absolutely nothing changed, consider retracting the bump or merging it with the next meaningful patch.
packages/coze-js/CHANGELOG.json (1)
8-14: Confirmed existing “none” change typeThe grep output shows that
"none"is already used alongside"minor"and"patch"inpackages/coze-js/CHANGELOG.json, so it’s supported by your current tooling. No changes needed here.
3 participants
Summary by CodeRabbit
Bug Fixes
Chores