Conversation
|
Caution Review failedThe pull request is closed. ℹ️ 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)
📝 WalkthroughWalkthroughFour package manifests have their ChangesUnified Version Bump
Release Tag Validation Tightening
Estimated code review effort🎯 3 (Moderate) | ⏱️ ~20 minutes Possibly related PRs
Suggested labels
Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 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: 9/10 reviews remaining, refill in 6 minutes. Comment |
![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 the current code and only fix it if needed.
Inline comments:
In `@packages/util/package.json`:
- Line 3: The package.json "version" field currently uses a 4-part version
string ("2026.5.2.2") which is not semver-compliant; update the "version" value
in packages/util/package.json to a strict semver format such as "2026.5.2-2" (or
X.Y.Z-prerelease) and make the same change consistently across any other bumped
manifests (other package.json files or lockfiles) to avoid npm/Bun rejection;
search for "version": "2026.5.2.2" and replace with the chosen semver string,
then run your usual CI/versioning checks.
🪄 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: c248c6d7-dc92-4293-a9b3-77dd9c8f6667
⛔ Files ignored due to path filters (1)
bun.lockis excluded by!**/*.lock
📒 Files selected for processing (4)
packages/app/package.jsonpackages/desktop-electron/package.jsonpackages/opencode/package.jsonpackages/util/package.json
| { | ||
| "name": "@opencode-ai/util", | ||
| "version": "2026.5.2", | ||
| "version": "2026.5.2.2", |
There was a problem hiding this comment.
🧩 Analysis chain
🌐 Web query:
Do npm and Bun accept a package.json version formatted as 2026.5.2.2, or must it be strict SemVer (e.g., 2026.5.2-2)?
💡 Result:
npm and Bun do not accept a package.json "version" formatted as 2026.5.2.2. They expect the version string to be valid SemVer (SemVer “normal version” is X.Y.Z with optional prerelease like -2). Use something like 2026.5.2-2 (or 2026.5.2+build, etc.), not a fourth dot-separated numeric component. Why: - npm states that the package.json "version" must be parseable by node-semver. - node-semver and SemVer’s “normal version” format require exactly three numeric dot-separated components (X.Y.Z); prerelease is introduced with a hyphen. - Bun’s semver implementation is designed to be compatible with node-semver, and Bun’s semver API returns false for invalid versions.
Citations:
- 1: https://docs.npmjs.com/cli/v11/configuring-npm/package-json/
- 2: https://docs.npmjs.com/cli/v6/using-npm/semver/
- 3: https://semver.org/
- 4: https://docs.npmjs.com/about-semantic-versioning/
- 5: https://bun.sh/docs/runtime/semver
- 6: https://docs.npmjs.com/cli/v9/configuring-npm/package-json/?v=true
Use a semver-compatible version format on Line 3.
2026.5.2.2 is a 4-segment version and is rejected by npm and Bun, which require strict SemVer (X.Y.Z with optional prerelease using hyphen). Use 2026.5.2-2 instead and apply it consistently across all bumped manifests.
Suggested manifest change
- "version": "2026.5.2.2",
+ "version": "2026.5.2-2",📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| "version": "2026.5.2.2", | |
| "version": "2026.5.2-2", |
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@packages/util/package.json` at line 3, The package.json "version" field
currently uses a 4-part version string ("2026.5.2.2") which is not
semver-compliant; update the "version" value in packages/util/package.json to a
strict semver format such as "2026.5.2-2" (or X.Y.Z-prerelease) and make the
same change consistently across any other bumped manifests (other package.json
files or lockfiles) to avoid npm/Bun rejection; search for "version":
"2026.5.2.2" and replace with the chosen semver string, then run your usual
CI/versioning checks.
![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 updates the version of the @opencode-ai/app, @opencode-ai/desktop-electron, opencode, and @opencode-ai/util packages from 2026.5.2 to 2026.5.2.2. Feedback was provided regarding the bun.lock file, where the version fields for these packages were removed instead of being updated. It is recommended to run bun install to properly synchronize the lockfile with the package.json changes and maintain consistency.
| "packages/app": { | ||
| "name": "@opencode-ai/app", | ||
| "version": "2026.5.2", | ||
| "dependencies": { |
There was a problem hiding this comment.
The version field for @opencode-ai/app was removed from the lockfile. Since the version is being bumped in package.json, it should be updated in the lockfile as well to maintain consistency. It is recommended to run bun install to properly update the lockfile.
"version": "2026.5.2.2",
"dependencies": {
| "packages/desktop-electron": { | ||
| "name": "@opencode-ai/desktop-electron", | ||
| "version": "2026.5.2", | ||
| "dependencies": { |
There was a problem hiding this comment.
The version field for @opencode-ai/desktop-electron was removed from the lockfile. Since the version is being bumped in package.json, it should be updated in the lockfile as well to maintain consistency. It is recommended to run bun install to properly update the lockfile.
"version": "2026.5.2.2",
"dependencies": {
| "packages/opencode": { | ||
| "name": "opencode", | ||
| "version": "2026.5.2", | ||
| "bin": { |
There was a problem hiding this comment.
The version field for opencode was removed from the lockfile. Since the version is being bumped in package.json, it should be updated in the lockfile as well to maintain consistency. It is recommended to run bun install to properly update the lockfile.
"version": "2026.5.2.2",
"bin": {
| "packages/util": { | ||
| "name": "@opencode-ai/util", | ||
| "version": "2026.5.2", | ||
| "dependencies": { |
There was a problem hiding this comment.
The version field for @opencode-ai/util was removed from the lockfile. Since the version is being bumped in package.json, it should be updated in the lockfile as well to maintain consistency. It is recommended to run bun install to properly update the lockfile.
"version": "2026.5.2.2",
"dependencies": {
Astro-Han
force-pushed
the
release/v2026.5.2.2
branch
from
8302208 to
05cab71
Compare
Astro-Han
changed the title
1 participant
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