chore(deps): migrate z3 bundled feature to vendored
@purp 已经在做这个了。
开始于 2026年9月22日。
评估
这个 Issue 还没有评估数据。
描述
Description
z3 0.21 deprecates the bundled feature in favor of vendored. z3-sys
0.13's build script emits cargo:warning=The 'bundled' feature is deprecated. Please use the 'vendored' feature. on every build that enables it.
OpenShell wires the deprecated name through its own feature aliases:
crates/openshell-prover/Cargo.toml:14—bundled-z3 = ["z3/bundled"]crates/openshell-prover-cli/Cargo.toml:18,crates/openshell-server/Cargo.toml:123,
crates/openshell-gateway/Cargo.toml:75forwardbundled-z3onward
The work is to decide whether to repoint the bundled-z3 alias at
z3/vendored, and whether the public-facing alias name should change with it.
Context
Both features currently resolve to the same z3-sys code path, so nothing is
broken today and there is no user-visible behavior change. This is
forward-maintenance: the deprecated name will eventually be removed upstream.
This path is not incidental — it is the release build path. tasks/ci.toml:34
and tasks/scripts/stage-prebuilt-binaries.sh:172-173 force bundled-z3 for
the gateway, so tagged releases compile Z3 from vendored source through it.
That makes the change low-urgency but not zero-risk, which is why it was kept
out of the z3 0.21 upgrade (#3552) and its documentation follow-up.
bundled-z3 also appears in contributor-facing docs (README.md:362,
CONTRIBUTING.md:312-363) and in .agents/skills/build-openshell-mxc-windows/SKILL.md,
so a rename would need those updated in the same branch.
Not required for 0.1.0.
Definition of Done
- A decision is recorded on whether to repoint
bundled-z3atz3/vendored
and whether to rename the alias - If repointed, the gateway release build and the prover test suite are
verified against the vendored path - Contributor docs and the Windows build skill match the resulting feature
names - No deprecation warning is emitted for the Z3 source-build path
- 主要语言
- Rust
- 星标
- 8.7k
- 派生
- 1.3k
- 平均合并
- 2 天 6 小时
- 30 天内合并 PR
- 297
贡献指南
从这里开始
- 先读完整个 Issue,再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库,在一个分支上完成修改。
- 提交 Pull Request,并在描述里引用这个 Issue 编号。
NVIDIA/OpenShell 的其他 Issue
-
area:docs
难度 1/5 1 小时以内 新手友好度 88/100
-
state:triage-needed
难度 2/5 1-3 小时 新手友好度 82/100
-
area:cli state:validated
难度 2/5 1-3 小时 新手友好度 72/100
-
state:triage-needed
难度 1/5 1 小时以内 新手友好度 90/100
-
area:build spike state:review-ready state:stale
难度 2/5 半天 新手友好度 68/100
相似的 Issue
-
难度 2/5 1-3 小时 新手友好度 75/100
TheLarkInn/aipm#2413 ·
-
documentation
难度 1/5 1 小时以内 新手友好度 90/100
alexgorbatchev/simple-ptt#15 ·
-
tooling
难度 2/5 1-3 小时 新手友好度 75/100
-
todo:ticket
难度 2/5 1-3 小时 新手友好度 70/100
-
难度 2/5 1-3 小时 新手友好度 75/100
taikoxyz/taiko-mono#22168 · 1 条评论 ·