Release v3.58.1#495
Conversation
navedmerchant
requested review from
JamesRobert20,
edelauna,
hannesrudolph and
taltas
as code owners
|
Note Reviews pausedIt looks like this branch is under active development. To avoid overwhelming you with review comments due to an influx of new commits, CodeRabbit has automatically paused this review. You can configure this behavior by changing the Use the following commands to manage reviews:
Use the checkboxes below for quick actions:
📝 WalkthroughWalkthroughVersion 3.58.1 patch release coordinating version manifest, changelog documentation, and localized README announcements. Release workflow documentation updated to transition from changeset-based process to direct CHANGELOG.md editing with bracketed headings. ChangesPatch Release 3.58.1
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~3 minutes Suggested reviewers
Poem
🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
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. Comment |
navedmerchant
force-pushed
the
release/v3.58.1
branch
from
19ea1cc to
975da87
Compare
navedmerchant
requested a deployment
to
marketplace-production
GitHub Actions
Waiting
navedmerchant
force-pushed
the
release/v3.58.1
branch
from
975da87 to
b2f3cab
Compare
navedmerchant
requested a deployment
to
marketplace-production
GitHub Actions
Waiting
![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
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@src/package.json`:
- Line 6: The package.json version is "3.58.1" but the changelog heading uses
"## 3.58.1" (no brackets), so the release-note extraction (which expects "##
[3.58.1]") will miss it; fix by either updating the changelog heading to "##
[3.58.1]" to match the workflow or update the publish workflow's regex to accept
both formats (e.g., allow headings with or without brackets); search for the
version key in package.json and the changelog heading "## 3.58.1" and adjust one
of them so the release extractor sees the exact version string.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: defaults
Review profile: CHILL
Plan: Pro Plus
Run ID: 4b0d9b97-8ce3-47a0-9144-427d829ad6bb
📒 Files selected for processing (3)
CHANGELOG.mdREADME.mdsrc/package.json
✅ Files skipped from review due to trivial changes (2)
- CHANGELOG.md
- README.md
| "description": "%extension.description%", | ||
| "publisher": "ZooCodeOrganization", | ||
| "version": "3.58.0", | ||
| "version": "3.58.1", |
There was a problem hiding this comment.
Release-note extraction contract is inconsistent with this version bump.
With version set to 3.58.1, the publish workflow will look for ## [3.58.1], but the provided changelog entry is ## 3.58.1 (no brackets). That means this release likely falls back to generic notes instead of the 3.58.1 patch entry. Please align either the changelog heading format or the workflow regex before publishing.
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@src/package.json` at line 6, The package.json version is "3.58.1" but the
changelog heading uses "## 3.58.1" (no brackets), so the release-note extraction
(which expects "## [3.58.1]") will miss it; fix by either updating the changelog
heading to "## [3.58.1]" to match the workflow or update the publish workflow's
regex to accept both formats (e.g., allow headings with or without brackets);
search for the version key in package.json and the changelog heading "## 3.58.1"
and adjust one of them so the release extractor sees the exact version string.
There was a problem hiding this comment.
@navedmerchant confirmed — the publish workflow at .github/workflows/marketplace-publish.yml extracts release notes by matching ## [version] (with brackets), so ## 3.58.1 will be missed and the GitHub release will just get a generic Release v3.58.1 note.
Could you update the CHANGELOG.md heading to ## [3.58.1]?
(For context: v3.54.0 is the only release with real notes on the releases page because it's the only one that used brackets — every release since has silently fallen back to the generic message.)
Also, .roo/commands/release.md step 6/9 references pnpm changeset:version as the mechanism for generating the changelog, but in practice the changelog is written directly by the LLM — and consistently without brackets. Could you update that doc to drop the changeset step and explicitly note that changelog headings should use the ## [version] format to match the workflow?
There was a problem hiding this comment.
Seems like the humans are having a chat. I'll hop back into my burrow for now. If you need me again, just tag @coderabbitai in a new comment, and I'll come hopping out!
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
edelauna
left a comment
edelauna
left a comment
There was a problem hiding this comment.
Nice, I think we can leave the readme alone, but we should bump the version in the locales readme
|
This is undoubtedly very good news, and I am extremely grateful for your work. But And there is another very important unresolved problem And also remove junk from the repo and from our disks Dear Naved Merchant, I believe these bugs must be fixed immediately, right now. On a user-scale, this represents a huge loss of resources. Not to mention the strain on data centers and the environment. I just noticed this bug myself. |
|
@DScoNOIZ I agree with you in some regards. Duplicated words don't always mean a pure waste, but the prompts could definitely be optimized. Writing many automation proxies, I know that you also should adapt prompts to the model you are using. Actually, system prompts should be fully editable. We also have many other fix and feat PRs sitting here like a duck, getting old and forgotten by the original PR authors. This isn't optimal. How can we help you @edelauna and @nevermorec getting more stuff evaluated for quality and merged= |
Co-authored-by: edelauna <54631123+edelauna@users.noreply.github.com>
navedmerchant
force-pushed
the
release/v3.58.1
branch
from
e39f04a to
52c4473
Compare
|
@DScoNOIZ thanks for pointing out these issues, we will take a look. @kyr0 We are trying our best to review all the PRs as well as push new features to make Zoo Code the best AI assisted coding experience on the market. You can help get focus on important issues you want prioritize issues by posting it on the #prs channel on Discord :). Thank you for being a part of the community and pushing to make Zoo Code great! |
github-merge-queue
Bot
removed this pull request from the merge queue due to failed status checks
|
@navedmerchant I'm fighting on your side. I have a lot of ideas and plans for Roo (ZooCode). It's a lot of work, but I think it's truly the best free software out there. Although I've tried many different ones. Please read my manifesto; I believe we need to implement this urgently. I'm currently trying to implement it solo using ZooCode. The problem is, I'm not a programmer, I'm a Vibecoder. I'd be very interested to hear your expert opinion on my idea. It's simple: give agents a universal copy-paste manager. |
4 participants
Release preparation for v3.58.1. This PR includes the final version bump, changelog updates, and Marketplace README updates.
Changes
--no-absolute-filenamestar argument ([BUG] Semble download fails #491 by @kazenshi, PR Remove unsupported tar argument --no-absolute-filenames #492 by @kazenshi)Summary by CodeRabbit
Bug Fixes
Documentation