chore(deps): migrate z3 bundled feature to vendored
@purp ci sta già lavorando.
Dal 22/9/2026.
Valutazione
Questa issue non è ancora stata valutata.
Descrizione
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
- Lingua principale
- Rust
- Stelle
- 8.7k
- Fork
- 1.3k
- Merge medio
- 2g 8h
- PR unite (30g)
- 271
Guida per i contributori
Apri la guida per i contributori
Come iniziare
- Leggi tutta la issue e poi la guida ai contributi del progetto.
- Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
- Fai un fork del repository e lavora su un branch.
- Apri una pull request che faccia riferimento al numero della issue.
Altre issue di NVIDIA/OpenShell
-
area:docs
Difficoltà 1/5 Meno di un'ora Idoneità per principianti 88/100
-
state:triage-needed
Difficoltà 2/5 1-3 ore Idoneità per principianti 82/100
-
area:cli state:validated
Difficoltà 2/5 1-3 ore Idoneità per principianti 72/100
-
state:triage-needed
Difficoltà 1/5 Meno di un'ora Idoneità per principianti 90/100
-
area:build spike state:review-ready state:stale
Difficoltà 2/5 Mezza giornata Idoneità per principianti 68/100
Tutte le issue di NVIDIA/OpenShell
Issue simili
-
Browser (wasm) relay client cannot connect to relays whose URL has a trailing-dot FQDN hostname Aperta
Difficoltà 2/5 1-3 ore Idoneità per principianti 75/100
n0-computer/iroh#4550 ·
-
impl detach for native Aperta
Difficoltà 2/5 1-3 ore Idoneità per principianti 65/100
paritytech/zombienet-sdk#591 ·
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 75/100
farion1231/cc-switch#7638 · 1 commento ·
-
onnx-ir re-exports ModelProto and GraphProto but not NodeProto, AttributeProto and AttributeType Aperta
Difficoltà 2/5 1-3 ore Idoneità per principianti 75/100
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 75/100