chore(deps): 合入 gpui-kit 上游改动，gpui-shell 跟进到 0.6.4 - #258
Merged
Merged
Conversation
- gpui-kit（feigeCode/gpui-kit port-ce-generic-to-main）升到 23c8e5b78：合入上游 45 个提交（0.6.1 → 0.6.4）。其中 QuickJS JIT 升到 0.12.9，与本分支的 32 位改动 重叠，冲突已在 gpui-kit 侧解决（保留按位宽拆分 + i686 补丁；上游把软换行的行换成 `InputLine`、对话框 button props 改为合并语义，内联 widget 布局与 alert/confirm 已相应适配）。Cargo.toml 的 8 处 pin 一起回填到新 rev，Cargo.lock 重新解析 （gpui-wry 0.6.4、rquickjs 0.12.9，旧 rev 无残留）。 - 宿主 gpui-shell 版本 0.6.1 → 0.6.4：extension-runtime 的 GPUI_SHELL_VERSION 与 各处测试清单、文档示例同步提升。该校验对 0.x 按 minor 精确匹配，旧值会被直接拒绝。 验证：cargo check -p remote_desktop_view（新 gpui-kit + quickjs-jit i686 分支） → Finished dev profile，0 error。
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.
Description
feigeCode/gpui-kit(port-ce-generic-to-main) up to23c8e5b78, which merges the 45 upstream commits released between 0.6.1 and 0.6.4. Upstream bumped the QuickJS JIT to 0.12.9 in the very files our 32-bit work touches, so the fork keeps its per-target split and carries the i686 patch rebased onto 0.12.9 (feigeCode/quickjs-jitfix/i686-interpreter-only-0.12.9,2287cef70).gpui-shell0.6.1 → 0.6.4:extension-runtime'sGPUI_SHELL_VERSIONand every test fixture / doc example declaringengines.gpui_shellfollow. The check matches0.xby minor exactly, so a stale value is rejected outright.gpui-kitpin sites inCargo.tomlmove together, andCargo.lockre-resolves (gpui-wry0.6.4,rquickjs0.12.9, no stale revision left).crates/shell; keep our gutter-lane and inline-widget code next to upstream'stoken_element; upstream's newInputLinerows carrylenas a field and have nosplit_at, so it gained one (delegating to the innerShapedLine, passing a token row through whole) to keep the inline-widget layout reserving room between two runs of a row;DialogButtonPropsis merged rather than replaced now, soalert()/confirm()go through theshow_cancel(..)builder and the footer readsis_cancel_shown().Break Changes
engines.gpui_shellbelow0.6.4— the0.2.0plugin manifests for instance — are rejected by the host, exactly as the earlier 0.6.1 bump already did.How to Test
cargo check -p remote_desktop_viewagainst the new gpui-kit revision and the i686 quickjs-jit branch: finishes with 0 errors.cargo test -p extension-runtime: 214 tests pass. The wasm contract fixture needs the workspace-wide feature unification, so the suite has to run ascargo test --all, the way CI runs it.