chore: upstream fetch by DevFlex-AI · Pull Request #67 · bolt-builder/bolt-cli

DevFlex-AI · 2026-07-31T05:47:05Z

Issue for this PR

Closes #68

Type of change

Bug fix
New feature
Refactor / code improvement
Documentation

What does this PR do?

Pulls in upstream changes via two commits:

fix(app): prevent stale session tab reads (#39767): fixes the app reading stale session tab state.
feat(go): add GPT 5.6 Luna content (#39812): adds GPT 5.6 Luna content to the go/zen docs, console i18n strings, and related routes.

The changes are taken as-is from upstream, so they work for the same reasons they work upstream.

How did you verify your code works?

The commits are unmodified upstream changes; verification relies on this repository's CI checks on this PR. The author should confirm any additional local testing.

Screenshots / recordings

If this is a UI change, please include a screenshot or recording.

Checklist

I have tested my changes locally
I have not included unrelated changes in this PR

If you do not follow this template your PR will be automatically rejected.

^{Need help on this PR? Tag @codesmith-bot with what you need. Autofix is enabled.}

coderabbitai · 2026-07-31T05:47:13Z

Warning

Review limit reached

@DevFlex-AI, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 1 minute

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 4ada9e2f-08ba-44dd-b3a8-2e3e3cdd009e

📥 Commits

Reviewing files that changed from the base of the PR and between fd52a06 and da59457.

📒 Files selected for processing (59)

packages/app/src/components/session/session-header.tsx
packages/app/src/components/titlebar-tab-nav.tsx
packages/app/src/pages/new-session/new-session-view.tsx
packages/console/app/src/i18n/ar.ts
packages/console/app/src/i18n/br.ts
packages/console/app/src/i18n/da.ts
packages/console/app/src/i18n/de.ts
packages/console/app/src/i18n/en.ts
packages/console/app/src/i18n/es.ts
packages/console/app/src/i18n/fr.ts
packages/console/app/src/i18n/it.ts
packages/console/app/src/i18n/ja.ts
packages/console/app/src/i18n/ko.ts
packages/console/app/src/i18n/no.ts
packages/console/app/src/i18n/pl.ts
packages/console/app/src/i18n/ru.ts
packages/console/app/src/i18n/th.ts
packages/console/app/src/i18n/tr.ts
packages/console/app/src/i18n/uk.ts
packages/console/app/src/i18n/zh.ts
packages/console/app/src/i18n/zht.ts
packages/console/app/src/routes/go/index.tsx
packages/console/app/src/routes/workspace/[id]/go/lite-section.tsx
packages/web/src/content/docs/ar/go.mdx
packages/web/src/content/docs/ar/zen.mdx
packages/web/src/content/docs/bs/go.mdx
packages/web/src/content/docs/bs/zen.mdx
packages/web/src/content/docs/da/go.mdx
packages/web/src/content/docs/da/zen.mdx
packages/web/src/content/docs/de/go.mdx
packages/web/src/content/docs/de/zen.mdx
packages/web/src/content/docs/es/go.mdx
packages/web/src/content/docs/es/zen.mdx
packages/web/src/content/docs/fr/go.mdx
packages/web/src/content/docs/fr/zen.mdx
packages/web/src/content/docs/go.mdx
packages/web/src/content/docs/it/go.mdx
packages/web/src/content/docs/it/zen.mdx
packages/web/src/content/docs/ja/go.mdx
packages/web/src/content/docs/ja/zen.mdx
packages/web/src/content/docs/ko/go.mdx
packages/web/src/content/docs/ko/zen.mdx
packages/web/src/content/docs/nb/go.mdx
packages/web/src/content/docs/nb/zen.mdx
packages/web/src/content/docs/pl/go.mdx
packages/web/src/content/docs/pl/zen.mdx
packages/web/src/content/docs/pt-br/go.mdx
packages/web/src/content/docs/pt-br/zen.mdx
packages/web/src/content/docs/ru/go.mdx
packages/web/src/content/docs/ru/zen.mdx
packages/web/src/content/docs/th/go.mdx
packages/web/src/content/docs/th/zen.mdx
packages/web/src/content/docs/tr/go.mdx
packages/web/src/content/docs/tr/zen.mdx
packages/web/src/content/docs/zen.mdx
packages/web/src/content/docs/zh-cn/go.mdx
packages/web/src/content/docs/zh-cn/zen.mdx
packages/web/src/content/docs/zh-tw/go.mdx
packages/web/src/content/docs/zh-tw/zen.mdx

_{Comment @coderabbitai help to get the list of available commands.}

vercel · 2026-07-31T05:47:14Z

@MrMushrooooom is attempting to deploy a commit to the adevloper152's projects Team on Vercel.

A member of the Team first needs to authorize it.

github-actions · 2026-07-31T05:47:14Z

Hey! Your PR title upstream fetch doesn't follow conventional commit format.

Please update it to start with one of:

feat: or feat(scope): new feature
fix: or fix(scope): bug fix
docs: or docs(scope): documentation changes
chore: or chore(scope): maintenance tasks
refactor: or refactor(scope): code refactoring
test: or test(scope): adding or updating tests

Where scope is the package name (e.g., app, desktop, opencode).

See CONTRIBUTING.md for details.

github-actions · 2026-07-31T05:47:14Z

This PR doesn't fully meet our contributing guidelines and PR template.

What needs to be fixed:

Not all checklist items are checked. Please confirm you have tested locally and have not included unrelated changes.

Please edit this PR description to address the above within 2 hours, or it will be automatically closed.

If you believe this was flagged incorrectly, please let a maintainer know.

DevFlex-AI · 2026-07-31T05:47:27Z

@codesmith-bot does this have branding of opencode?

github-actions · 2026-07-31T05:47:46Z

The following comment was made by an LLM, it may be inaccurate:

deepsource-io · 2026-07-31T05:48:01Z

DeepSource Code Review

We reviewed changes in fd52a06...da59457 on this pull request. Below is the summary for the review, and you can see the individual issues we found as inline review comments.

See full review on DeepSource ↗

PR Report Card

Overall Grade Focus Area: Reliability	Security Reliability Complexity Hygiene

Code Review Summary

Analyzer	Updated (UTC)	Details
JavaScript	Jul 31, 2026 5:47a.m.	Review ↗
Shell	Jul 31, 2026 5:47a.m.	Review ↗
Secrets	Jul 31, 2026 5:47a.m.	Review ↗
Docker	Jul 31, 2026 5:47a.m.	Review ↗
Python	Jul 31, 2026 5:47a.m.	Review ↗
CSS	Jul 31, 2026 5:47a.m.	Review ↗
Rust	Jul 31, 2026 5:47a.m.	Review ↗
Ruby	Jul 31, 2026 5:47a.m.	Review ↗
Swift	Jul 31, 2026 5:47a.m.	Review ↗
PHP	Jul 31, 2026 5:47a.m.	Review ↗
Lua	Jul 31, 2026 5:47a.m.	Review ↗
Java	Jul 31, 2026 5:47a.m.	Review ↗
Go	Jul 31, 2026 5:47a.m.	Review ↗
C & C++	Jul 31, 2026 5:47a.m.	Review ↗
Ansible	Jul 31, 2026 5:47a.m.	Review ↗
Apex	Jul 31, 2026 5:47a.m.	Review ↗
Elixir	Jul 31, 2026 5:47a.m.	Review ↗
Groovy	Jul 31, 2026 5:47a.m.	Review ↗
Objective-C	Jul 31, 2026 5:47a.m.	Review ↗
PowerShell	Jul 31, 2026 5:47a.m.	Review ↗
Terraform	Jul 31, 2026 5:47a.m.	Review ↗
VB.NET	Jul 31, 2026 5:47a.m.	Review ↗
SQL	Jul 31, 2026 5:47a.m.	Review ↗
Scala	Jul 31, 2026 5:47a.m.	Review ↗
Perl	Jul 31, 2026 5:47a.m.	Review ↗
Kotlin	Jul 31, 2026 5:47a.m.	Review ↗
Helm	Jul 31, 2026 5:47a.m.	Review ↗
Erlang	Jul 31, 2026 5:47a.m.	Review ↗
Dart	Jul 31, 2026 5:47a.m.	Review ↗
C#	Jul 31, 2026 5:47a.m.	Review ↗

Important

AI Review is run only on demand for your team. We're only showing results of static analysis review right now. To trigger AI Review, comment @deepsourcebot review on this thread.

github-actions · 2026-07-31T05:48:49Z

Thanks for your contribution!

This PR doesn't have a linked issue. All PRs must reference an existing issue.

Please:

Open an issue describing the bug/feature (if one doesn't exist)
Add Fixes #<number> or Closes #<number> to this PR description

See CONTRIBUTING.md for details.

blacksmith-sh · 2026-07-31T05:48:56Z

@DevFlex-AI

@codesmith-bot does this have branding of opencode?

The diff itself introduces OpenCode branding in one place: every locale's go.mdx/zen.mdx docs table gains a "GPT 5.6 Luna" row whose endpoint is https://opencode.ai/zen/go/v1/responses (18 added lines total). The rest of the PR (Solid keyed fixes in packages/app, i18n model-list updates) doesn't add branding, but the surrounding files it touches are full of it: the i18n strings being edited live next to keys like "go.title": "OpenCode Go | ...", and the docs pages are the OpenCode Go/Zen product docs.

That's expected given what this PR is: its head branch is literally anomalyco/opencode's dev branch (head SHA da59457), so it's syncing upstream OpenCode commits into this fork. The repo as a whole still carries OpenCode branding everywhere (package names like @opencode-ai/core, the packages/opencode package, opencode.ai docs content), and this PR neither adds to nor removes any of that beyond the endpoint URLs noted above. If the goal is a rebranded fork, the branding cleanup would be a separate de-branding pass, not something to block this sync on, since every upstream fetch will keep pulling these strings in.

DevFlex-AI · 2026-07-31T05:52:32Z

@DevFlex-AI

@codesmith-bot does this have branding of opencode?

The diff itself introduces OpenCode branding in one place: every locale's go.mdx/zen.mdx docs table gains a "GPT 5.6 Luna" row whose endpoint is https://opencode.ai/zen/go/v1/responses (18 added lines total). The rest of the PR (Solid keyed fixes in packages/app, i18n model-list updates) doesn't add branding, but the surrounding files it touches are full of it: the i18n strings being edited live next to keys like "go.title": "OpenCode Go | ...", and the docs pages are the OpenCode Go/Zen product docs.

That's expected given what this PR is: its head branch is literally anomalyco/opencode's dev branch (head SHA da59457), so it's syncing upstream OpenCode commits into this fork. The repo as a whole still carries OpenCode branding everywhere (package names like @opencode-ai/core, the packages/opencode package, opencode.ai docs content), and this PR neither adds to nor removes any of that beyond the endpoint URLs noted above. If the goal is a rebranded fork, the branding cleanup would be a separate de-branding pass, not something to block this sync on, since every upstream fetch will keep pulling these strings in.

well i am jsut syaing user facing ones i am fine if it just opencode.ai docs and url ednpoints

blacksmith-sh · 2026-07-31T05:52:57Z

@DevFlex-AI

@DevFlex-AI

@codesmith-bot does this have branding of opencode?

The diff itself introduces OpenCode branding in one place: every locale's go.mdx/zen.mdx docs table gains a "GPT 5...

Then this PR is fine by your criteria. The only user-facing UI code it touches is packages/app (pure Solid keyed refactors, no text changes) and the console's Go pages (packages/console), where the added strings are just model names like "GPT 5.6 Luna" in the model lists and limits graph. No new user-facing "OpenCode" text is introduced anywhere in the diff; every added OpenCode mention is either an https://opencode.ai/zen/go/v1/... endpoint URL or lives in the packages/web docs pages, both of which you said are acceptable. The "OpenCode Go" strings visible in the i18n hunks are pre-existing context lines, not additions from this sync.

DevFlex-AI · 2026-07-31T05:55:29Z

@DevFlex-AI

@DevFlex-AI

@codesmith-bot does this have branding of opencode?

The diff itself introduces OpenCode branding in one place: every locale's go.mdx/zen.mdx docs table gains a "GPT 5...

Then this PR is fine by your criteria. The only user-facing UI code it touches is packages/app (pure Solid keyed refactors, no text changes) and the console's Go pages (packages/console), where the added strings are just model names like "GPT 5.6 Luna" in the model lists and limits graph. No new user-facing "OpenCode" text is introduced anywhere in the diff; every added OpenCode mention is either an https://opencode.ai/zen/go/v1/... endpoint URL or lives in the packages/web docs pages, both of which you said are acceptable. The "OpenCode Go" strings visible in the i18n hunks are pre-existing context lines, not additions from this sync.

so can i merges yes or no?

blacksmith-sh · 2026-07-31T05:56:00Z

@DevFlex-AI

@DevFlex-AI

@DevFlex-AI

@codesmith-bot does this have branding of opencode?

The diff itself introduces OpenCode branding in one place: every locale's `go.m...

Yes. The PR is open and mergeable, and all real CI is green (typecheck, unit and e2e on Linux/Windows, nix-eval, standards/compliance checks). The two red checks are third-party noise, not code problems: Vercel failed because the deployment needs team authorization for the fork commit, and DeepSource's JavaScript analyzer flagged findings in the upstream code you're syncing, which you'd inherit on any upstream fetch anyway. Neither should block the merge unless your branch protection requires them.

OpeOginni and others added 2 commits July 31, 2026 05:14

fix(app): prevent stale session tab reads (#39767)

db4dbaa

feat(go): add GPT 5.6 Luna content (#39812)

da59457

github-actions Bot added needs:title needs:compliance labels Jul 31, 2026

github-actions Bot assigned DevFlex-AI Jul 31, 2026

DevFlex-AI changed the title ~~upstream fetch~~ chore: upstream fetch Jul 31, 2026

github-actions Bot added needs:issue and removed needs:title labels Jul 31, 2026

DevFlex-AI mentioned this pull request Jul 31, 2026

chore: sync upstream changes into dev #68

Closed

github-actions Bot removed the needs:issue label Jul 31, 2026

DevFlex-AI merged commit ba2adba into bolt-builder:dev Jul 31, 2026
48 of 50 checks passed

Uh oh!

Conversation

DevFlex-AI commented Jul 31, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Issue for this PR

Type of change

What does this PR do?

How did you verify your code works?

Screenshots / recordings

Checklist

Uh oh!

coderabbitai Bot commented Jul 31, 2026

Review limit reached

Uh oh!

vercel Bot commented Jul 31, 2026

Uh oh!

github-actions Bot commented Jul 31, 2026

Uh oh!

github-actions Bot commented Jul 31, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

DevFlex-AI commented Jul 31, 2026

Uh oh!

github-actions Bot commented Jul 31, 2026

Uh oh!

deepsource-io Bot commented Jul 31, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

DeepSource Code Review

PR Report Card

Code Review Summary

Uh oh!

github-actions Bot commented Jul 31, 2026

Uh oh!

blacksmith-sh Bot commented Jul 31, 2026

Uh oh!

DevFlex-AI commented Jul 31, 2026

Uh oh!

blacksmith-sh Bot commented Jul 31, 2026

Uh oh!

DevFlex-AI commented Jul 31, 2026

Uh oh!

blacksmith-sh Bot commented Jul 31, 2026

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

DevFlex-AI commented Jul 31, 2026 •

edited

Loading

github-actions Bot commented Jul 31, 2026 •

edited

Loading

deepsource-io Bot commented Jul 31, 2026 •

edited

Loading