chore(deps): migrate z3 bundled feature to vendored
@purp is already working on this.
Since Sep 22, 2026.
Assessment
This issue has not been assessed yet.
Description
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
- Dominant language
- Rust
- Stars
- 8.7k
- Forks
- 1.3k
- Avg merge
- 2d 8h
- Merged PRs (30d)
- 271
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from NVIDIA/OpenShell
-
area:docs
Difficulty 1/5 Under an hour Newbie friendliness 88/100
-
state:triage-needed
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
area:cli state:validated
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
state:triage-needed
Difficulty 1/5 Under an hour Newbie friendliness 90/100
-
area:build spike state:review-ready state:stale
Difficulty 2/5 Half a day Newbie friendliness 68/100
All issues in NVIDIA/OpenShell
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Eynzof/Hermes-CN-Desktop#616 ·
-
bug rules
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
app bug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
IronCoreLabs/ironcore-alloy#346 ·
-
good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 65/100