chore(release): bump v2026.5.3 - #385
Merged
Merged
Conversation
Contributor
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Plus Run ID: ⛔ Files ignored due to path filters (1)
📒 Files selected for processing (6)
✅ Files skipped from review due to trivial changes (5)
🚧 Files skipped from review as they are similar to previous changes (1)
📝 WalkthroughWalkthroughPackage versions in four workspaces were bumped from ChangesPackage Version Bumps
Release Tag Validation
Estimated code review effort🎯 2 (Simple) | ⏱️ ~12 minutes Possibly related PRs
Suggested labels
🚥 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 docstrings
🧪 Generate unit tests (beta)
Review rate limit: 8/10 reviews remaining, refill in 11 minutes and 25 seconds. Comment |
![gemini-code-assist[bot]](https://avatars.githubusercontent.com/in/956858?s=60&v=4){kind=small}
There was a problem hiding this comment.
Code Review
This pull request removes support for 4-segment CalVer versions in the release verification script and updates the test suite to reflect this change. It also removes version fields from the lockfile. However, the package versions in several package.json files were updated to a 4-segment format (2026.5.2.2), which contradicts the new validation logic and will cause the verification script to fail. Feedback was provided to use a 3-segment version instead.
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
Contributor
There was a problem hiding this comment.
Actionable comments posted: 4
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In `@packages/app/package.json`:
- Line 3: Update the package manifest version in packages/app/package.json by
changing the "version" field value from "2026.5.2.2" to "2026.5.3" so the
workspace publishes the correct release; locate the "version" property in the
package.json (the "version" key) and replace its string value accordingly to
match the other packages.
In `@packages/desktop-electron/package.json`:
- Line 4: Update the "version" field in package.json for the desktop-electron
package from "2026.5.2.2" to "2026.5.3" to remove the unsupported 4-segment
version format; locate the "version" key in packages' package.json (the entry
currently set to "2026.5.2.2") and change it to "2026.5.3", then run any project
version checks or CI that validate package metadata.
In `@packages/opencode/package.json`:
- Line 3: Update the package manifest's version property for the opencode
package by changing the "version" field in packages/opencode's package.json from
"2026.5.2.2" to "2026.5.3"; ensure you only modify the "version" value (the JSON
"version" key) so the release metadata matches the intended bump.
In `@packages/util/package.json`:
- Line 3: Update the package.json "version" field from the four-segment CalVer
string currently set to "2026.5.2.2" to the intended release version "2026.5.3";
locate the "version" key in packages/util/package.json and replace its value so
the manifest uses the supported three-segment CalVer expected by the release
tooling.
🪄 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: Path: .coderabbit.yaml
Review profile: CHILL
Plan: Pro Plus
Run ID: b1cc2135-eb92-4fa0-abc3-ca6884f35ac6
⛔ Files ignored due to path filters (1)
bun.lockis excluded by!**/*.lock
📒 Files selected for processing (6)
packages/app/package.jsonpackages/desktop-electron/package.jsonpackages/desktop-electron/scripts/verify-release.test.tspackages/desktop-electron/scripts/verify-release.tspackages/opencode/package.jsonpackages/util/package.json
Astro-Han
force-pushed
the
release/v2026.5.3
branch
from
May 2, 2026 12:57
05cab71 to
6b3ddd1
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Bump version from 2026.5.2 to 2026.5.3 for the second release today.
Also reverts the 4-segment CalVer support from #374 — the 4-segment format
is incompatible with
electron-builderandelectron-updater, which bothuse npm
semverfor validation and comparison.Why
Second same-day release. 4-segment CalVer (
2026.5.2.2) is rejected byapp-builder-libat build time and byelectron-updaterat runtime.Revert to 3-segment bumping for same-day releases.
Related Issue
None.
Human Review Status
Pending.
Review Focus
Risk Notes
None — version bump only.
How To Verify
Checklist
dev, and my PR title and commit messages use Conventional Commits in EnglishSummary by CodeRabbit