Dependabot can't fix the zip alerts: connector_arrow pins a duckdb that needs zip 6

Aperta
#6,517 1 commento 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 3 giorni

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
1-2 giorni
Idoneità per principianti
12/100
Tipo di issue
Bug
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
rust

Direzione di ricerca

The vulnerable zip 6.0.0 enters Cargo.lock through libduckdb-sys, pulled in by the test-dbs feature, and the blocker is the duckdb version pinned by connector_arrow. Start by reading the duckdb and connector_arrow entries in the workspace Cargo.toml files and the linked upstream PRs. Done means a prqlc build no longer resolves zip 6 and the Dependabot alerts close, which depends on an upstream connector_arrow release first.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

Dependabot alerts #217–#220 flag zip 6.0.0 in Cargo.lock. #217 (GHSA-m665-v7pm-7grj) is critical and patched in 9.0.5. The others (GHSA-q7v9-x93c-xqv3, GHSA-8hxf-qr8p-62x4, GHSA-9hj8-73fh-9963) are patched in 9.0.0. Dependabot couldn't open a fix (run ended in security_update_not_possible, with 6.0.0 as the highest resolvable version), and no lockfile-only bump reaches it.

Why it's stuck: zip is a build-script dependency of libduckdb-sys, which comes in only through the test-dbs features (duckdb for the integration tests). prqlc users don't build it. libduckdb-sys 1.10501.0 (on main) and 1.10505.0 (with #6515) both require zip ^6. 1.10506.1 moves to zip ^9, and 1.20000.x drops zip. But connector_arrow pins duckdb with a tilde requirement (~1.10501.0 in 0.11.0, ~1.10505.0 in the latest release, 0.12.2), and prqlc has to use the same duckdb as connector_arrow to hand it a connection.

What would fix it: a connector_arrow release from its current main. aljazerzen/connector_arrow#84 (merged 2026-10-08) moved it to duckdb ~1.10506.0, which resolves to 1.10506.1 and so to zip 9.x. aljazerzen/connector_arrow#87 (open) would go further, to ~1.20000.0. After that release, prqlc needs a connector_arrow bump with the matching duckdb minimum, building on #6515.

#6445 covered the same chain when zip briefly yanked its pre-9 releases.

Lingua principale
Rust
Stelle
10.9k
Fork
261
Merge medio
3g 21h
PR unite (30g)
84

Preparare l'ambiente

Apri in Codespaces

Avvia il container di sviluppo del progetto nel browser, con il tuo account GitHub.

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di PRQL/prql

Tutte le issue di PRQL/prql

Issue simili

Altre issue su Rust

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.