Uh oh!
There was an error while loading. Please reload this page.
chore(deps-dev): bump storybook from 8.6.15 to 8.6.17 - #772
Merged
github-actions[bot] merged 1 commit intoFeb 23, 2026
Conversation
Bumps [storybook](https://github.com/storybookjs/storybook/tree/HEAD/code/core) from 8.6.15 to 8.6.17. - [Release notes](https://github.com/storybookjs/storybook/releases) - [Changelog](https://github.com/storybookjs/storybook/blob/v8.6.17/CHANGELOG.md) - [Commits](https://github.com/storybookjs/storybook/commits/v8.6.17/code/core) --- updated-dependencies: - dependency-name: storybook dependency-version: 8.6.17 dependency-type: direct:development update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
ContributorAuthor
LabelsThe following labels could not be found: Please fix the above issues or remove invalid values from |
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Uh oh!
There was an error while loading. Please reload this page.
Contributor
❌ Console Performance Budget
📦 Bundle Size Report
Size Limits
|
os-zhuang added a commit
that referenced
this pull request
Jul 8, 2026
…st publish errors (cloud#771/#772) (#2351) Trust-polish batch from the 2026-07-09 magic-flow acceptance run (objectstack-ai/cloud#771, #772): - The chat surface now speaks the CONVERSATION's language: a Chinese thread under an English console got English canned approval messages ("Looks good — build it as proposed."), English progress labels and English starter chips. detectConversationLanguage() reads the latest user message (CJK → zh) and wins over the UI locale; falls back to the UI language for fresh threads. - Default agent tab prefers BUILD when the catalog offers it: the build surface is the one that resumes its in-progress conversation, so landing on the ask tab hid the user's build thread behind a tab switch ("my build chat disappeared" → they rebuild from scratch — the user-side path of cloud#769). Ask-only users are unaffected. - Build persona stops masquerading as a data-Q&A box: its empty-state pitch and starter chips are now build-flavoured (zh + en), instead of the ask persona's "query and analyze your data" copy with metadata chips. - Publish failure toast carries the real error: the handler threw `new Error(String(failedCount))`, so users saw "Publish failed — 2". Now it surfaces the first failed item's type/name/error (+N more) or the server error message. - The floating panel's publish success now pulses emitMetadataRefresh() (the full-page AI route already did), so the launcher/app switcher lists the new app WITHOUT a page reload — "open it from the launcher" was a lie until F5. - Re-hydrated tool-call-only turns no longer render their internal placeholder ("(called todo_write, propose_blueprint)") as prose; they collapse to a quiet localized activity note. Build green (turbo app-shell+plugin-chatbot), vitest 1242 passed. Co-authored-by: Claude Fable 5 <noreply@anthropic.com>
os-zhuang added a commit
that referenced
this pull request
Jul 14, 2026
…lier handoff card (#2458) (#2496) When the `ask` agent declines a build-shaped request, the ~20s wait before the "Open in Builder →" card is the LLM's time-to-tool-call. During it the chat could show dead air: a blank bubble, or the static "执行过程" activity note when the backend streamed a `(called …)` tool-call placeholder mid-stream. `ChatbotEnhanced` now renders the existing `ThinkingDots` indicator whenever a streaming assistant turn has nothing VISIBLE yet — whitespace-only content, a `(called …)` placeholder, or reasoning hidden in `summary` mode. The static "执行过程" note is kept only for FINISHED (re-hydrated) tool-call-only turns (#772 preserved). The `builderHandoff` card already renders at `output-available` with no prose gate, so it surfaces the instant the tool result lands; the typing cursor now only paints beside real streaming prose. Tests: card renders while streaming before prose; live dots (not 执行过程) for a mid-stream placeholder; 执行过程 note preserved for a finished placeholder turn. Co-authored-by: Jack Zhuang <277994282+os-zhuang@users.noreply.github.com> Co-authored-by: Claude Opus 4.8 <noreply@anthropic.com>
This was referenced Aug 8, 2026
akarma-synetal pushed a commit
to akarma-synetal/objectui
that referenced
this pull request
Aug 10, 2026
…3837) (objectstack-ai#3897) * fix(app-shell): 方案卡的 Building… 徽标随 UI 语言取值,不再被会话语言门控 (objectstack-ai#3837) `AiChatPage` 用 `convZh`(会话语言)门控四个字符串,因为 cloud 确认门 (`service-ai-studio` `confirm-gate.ts` `APPROVAL_RE`)只认中英,发进线程的 文本必须与线程本身同语言(objectstack-ai#772/objectstack-ai#2884)。该门上方注释的后半句写明了另一半规 则:button LABELS stay on the UI locale。 `planBuildingLabel`(objectstack-ai#2632 引入)落在了这句的错误一侧,中文会话恒取硬编码的 `正在搭建…`,两个后果都已实测: - **混合语言的卡片**:英文控制台里,中文会话的方案卡 `Proposed plan` / `Build it` / `Built` / `Not yet built` 全英文,中间夹一个中文徽标。objectstack-ai#2458 第 4 条记录的是同一个病的反方向。 - **翻译永远读不到**:中文会话恒走字面量,`console.ai.planBuilding` 的 zh 值对中文读者无效。objectstack-ai#3546 切片四(PR objectstack-ai#3839)刚把该 key 补进十包,只能做围 堵 —— 把 zh 值写成与字面量逐字节相同并把两者钉在一起。 徽标现在与相邻十二个标签一样读 `t('console.ai.planBuilding', …)`:十个包全 部可达(德文控制台 + 中文会话渲染 `Wird erstellt…`),zh 包成为该中文措辞的 唯一来源(值不变,中文读者看到的字符串与改动前完全一致)。 三条出站文本(`planApproveMessage` / `planApproveDefaultsMessage` / `changesConfirmMessage`)一行未动,仍随会话语言 —— 复核确认三者都交给 `onSendMessage`(`ChatbotEnhanced.tsx:1598`、`:2395`)、由门读取,正是 `convZh` 分支存在的那一类;全文件再无其它 `*Label`/`*Title` 被该门控住 (`convZh` 全部读点:定义 1 处 + 这三条)。 钉子: - `packages/app-shell/.../AiChatPage.planCardLocale.test.tsx`(新增)真渲染 `ChatPane` + 真 `I18nProvider` + 真 `isConversationZh`,把 `ChatbotEnhanced` 换成 props 记录器:en 控制台 + 中文会话 → `Building…` 且卡上 `*Label` 无一含中日韩字符;de 控制台 + 中文会话 → `Wird erstellt…` (三方语言证明是包在应答,而非两路三元);zh 控制台 → `正在搭建…`;三条 出站文本仍随会话。 - `packages/i18n/.../console-namespace-3546.test.tsx`:切片四埋的围堵钉按其 自述翻转 —— 从「字面量与 zh 包逐字节相同」改为钉住门已移除,并把不变量放 宽一步:`convZh` 只许门控出站 `*Message`,任何新读点都会红。 反向验证(方向先判后跑,与预判一致):还原三元 → 3 红 —— i18n 钉子按自定义 消息点名、en 控制台用例、de 控制台用例;zh 控制台用例与三条出站文本保持绿 (前者按设计逐字节相同,不具区分力,已在测试头注明)。 顺带:`conversationLanguage.ts` 模块头把 progress labels 也列进「随会话」, 该句在本改动后不再为真,收窄为「只治离开控制台发给 agent 的文本」。 写钉子时量到发送半边另有一个缺陷(zh 控制台 + 英文会话会把中文确认句发进英 文线程;`planAnswerMessage` 完全没有门控),不在本单范围,已立 objectstack-ai#3896。 测试:`packages/app-shell/src/console/ai` + `packages/i18n` 47 文件 654 通过; 两包 type-check 通过,全仓 `turbo run type-check` 78/78 通过;改动文件 eslint 零告警;`check-control-bytes` / `check-i18n-call-site-keys` / `check-i18n-en-drift` 均通过(零 en 值变更)。 Claude-Session: https://claude.ai/code/session_01GTRjn8xBqp75dk7kFupVRt Co-authored-by: Claude <noreply@anthropic.com> * test(app-shell): 钉子里的 agent 桩改用具名类型断言,不用 as never 评审可读性,零行为改动:`ChatPane` 的 agents 桩从 `as never` 改成 `as unknown as AgentDescriptor`(类型导入,运行期擦除;该模块在本文件里被 vi.mock,类型不受影响)。 Claude-Session: https://claude.ai/code/session_01GTRjn8xBqp75dk7kFupVRt Co-authored-by: Claude <noreply@anthropic.com> --------- Co-authored-by: Claude <noreply@anthropic.com>
akarma-synetal pushed a commit
to akarma-synetal/objectui
that referenced
this pull request
Aug 10, 2026
…ectstack-ai#3921) objectstack-ai#772 / objectstack-ai#2884 立下的规则写在 `AiChatPage` 的门上:出站文本随**会话**语言,渲染 标签随 UI 语言。规则只实现了一半 —— 三条出站文本写作 `convZh ? '<中文字面量>' : t('console.ai.…')`,而 `t()` 读的是 **UI 包**,于是 「非中文」那一支答的是 UI 语言、不是英文;第四条 `planAnswerMessage` 连门都没过。 两个方向各一个已实测后果: - **zh 控制台 + 英文会话发出中文。** zh 包定义了全部四个 key,所以 `t()` 是命中 而非落到英文 defaultValue:点 Build it,进英文线程的是 `确认，开始搭建。`。cloud 确认门(`service-ai-studio` `confirm-gate.ts` `APPROVAL_RE`)两种语言都认,构建 照走,agent 随后把整条线程转成中文 —— 即 objectstack-ai#2884 的症状、触发方向相反。 - **一键回答芯片两个方向都发 UI 语言。** 完全未门控:中文会话里发出 `For "…", go with: …`(objectstack-ai#772 开头那句抱怨的字面重演),zh 控制台下的英文会话里 发出中文句子。 四个站点现在统一走一个取值器 `outboundAgentText.ts`:中文会话取 `zh` 包该 key, 其余会话取 `en` 包该 key,永不读 UI 包。三个控制台 AI 界面(`/ai` 页、chat dock、 Studio copilot)都挂同一个 `ChatPane`,一并生效。 直接读两个包而不用 `t(key, { lng })` 是刻意的:i18next 的答案取决于宿主 app 装了 哪些 bundle 以及 `fallbackLng`,而 zh 查询静默回落到 en 正是上面那个错语言 bug。 取值器内的兜底表按语言分,并被钉成与两个包逐字节一致 —— 万一某个包不再定义该 key, 中文会话兜底到中文,绝不兜到英文。 标签未动:仍随 UI 语言。objectstack-ai#3837 那条「`*Label` 漂回会话门就红」的钉子现在同时守住 反向 —— 出站 `*Message` 被重新塞回 `t()` 也会红。 Claude-Session: https://claude.ai/code/session_01GTRjn8xBqp75dk7kFupVRt Co-authored-by: Claude <noreply@anthropic.com>
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 freeto join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Bumps storybook from 8.6.15 to 8.6.17.
Release notes
Sourced from storybook's releases.
Changelog
Sourced from storybook's changelog.
... (truncated)
Commits
c6e550aBump version from "8.6.16" to "8.6.17" [skip ci]9cf9d89Core: Require token for websocket connections7e51515Bump version from "8.6.15" to "8.6.16" [skip ci]Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)