Skip to content

chore(release): bump version to 0.39.6#2245

Open
lsm wants to merge 1 commit into
devfrom
release/v0.39.6
Open

chore(release): bump version to 0.39.6#2245
lsm wants to merge 1 commit into
devfrom
release/v0.39.6

Conversation

@lsm

@lsm lsm commented Jul 17, 2026

Copy link
Copy Markdown
Owner

Bump workspace and desktop bundle versions to 0.39.6 and add CHANGELOG entry for the 13 commits since v0.39.5, including the completed HyperNeo desktop rebrand, space task messaging fixes, GitHub polling improvements, and CI hardening.

@chatgpt-codex-connector

Copy link
Copy Markdown

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.

@lsm lsm left a comment

Copy link
Copy Markdown
Owner Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🤖 Review by glm-5.1 (GLM)

Model: glm-5.1 | Client: NeoKai | Provider: GLM

Recommendation: REQUEST_CHANGES — 1 P2 (quick fix, no code change)

Release v0.39.6 is well-formed overall. Verified: version bumps across all 11 files match the v0.39.5 release pattern exactly; all 13 commits since v0.39.5 are accurately represented in the CHANGELOG (count and content confirmed); date is correct; [Unreleased] handling is consistent with prior releases; packages/ui (independently versioned at 0.27.0), packages/skills, and root are correctly left untouched; CI is fully green; base/target is correctly dev with a single clean conventional commit.

One issue blocks:

P2 — bun.lock not regenerated (stale workspace versions)

The PR bumped all 6 workspace package.json files (cli, daemon, shared, web, e2e, desktop) to 0.39.6 and correctly regenerated Cargo.lock, but bun.lock was missed — it still records "version": "0.39.5" for those same 6 packages at bun.lock:17, 35, 53, 57, 73, 100. The next bun install anywhere will produce a dirty lockfile diff. This is the same lockfile-regeneration gap caught and fixed during the v0.39.0 review.

Fix: run bun install at the worktree root to regenerate bun.lock, commit, and push. No code changes needed.

Once bun.lock is regenerated, this is an APPROVE.

Note: the Codex review bot posted that it has hit its code-review usage limit and cannot review this PR, so no Codex +1 will be forthcoming this cycle.

@lsm
lsm force-pushed the release/v0.39.6 branch from 395c11a to 99facd4 Compare July 17, 2026 13:19

@lsm lsm left a comment

Copy link
Copy Markdown
Owner Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🤖 Review by glm-5.1 (GLM)

Model: glm-5.1 | Client: NeoKai | Provider: GLM

Recommendation: APPROVE — zero findings.

Round 2 (head 99facd4a5): the bun.lock P2 from round 1 is fixed and verified. All 6 workspace packages now read 0.39.6 (cli:17, daemon:35, desktop:53, e2e:57, shared:73, web:100); git grep "0.39.5" returns nothing outside CHANGELOG. Both bun.lock and Cargo.lock are regenerated and consistent with the bumped package.json files. The amended diff is exactly the version bumps + CHANGELOG + regenerated bun.lock — no unrelated changes.

Full re-verification on the new head:

  • Version bumps complete across all 12 files; matches the v0.39.5 release pattern
  • All 13 commits since v0.39.5 accurately represented in the CHANGELOG
  • CI fully green (run 29583499690 → success; no failures or cancellations)
  • Base = dev, clean conventional commit

Ready to release.

Note: the Codex review bot posted a code-review usage-limit message this cycle and has not reacted +1/eyes. Triggering @codex review as a final attempt; if it cannot review, proceeding per the timeout-window fallback with a recorded warning.

@lsm

lsm commented Jul 17, 2026

Copy link
Copy Markdown
Owner Author

@codex review

@chatgpt-codex-connector

Copy link
Copy Markdown

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.
To continue using code reviews, you can upgrade your account or add credits to your account and enable them for code reviews in your settings.

@chatgpt-codex-connector

Copy link
Copy Markdown

You have reached your Codex usage limits. You can see your limits in the Codex usage dashboard.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant