The repository now lives in the poli0981org organization, and this makes it at home there. - main was red since 2026-11-18: RUSTSEC-2026-0543 (chrono), in Cargo.lock only through serde_with's weak features and compiled into nothing; ignored with its reason and exit condition. - Supersedes #113–#118 (Rust 1.100.0, rusqlite 0.42.0, Tauri 2.12.6, code-health pins, actions, npm) plus jsdom 31.0.1; minimatch 11 closes GHSA-g3hv-75wg-m249. rfd 0.18 (#112) is held again until tauri-plugin-dialog moves. - Dependabot's tauri groups never worked (it picks the most specific group); exclude-patterns on the catch-alls fix it. - CI is self-contained: no workflow calls poli0981/.github; every action is pinned by commit; notify.yml vendors the Discord notifier. - npm licences: scripts/check-licenses.mjs, deny.toml's allowlist for the npm half. Required, with cargo deny and tauri lockstep — eight required checks. - Qodana in two parts (Rust, TS/JS), full scans, a triaged Rust baseline, fail on anything new. The Rust container needed its toolchain and CARGO_HOME pointed somewhere writable before it analysed anything. - SonarQube Cloud analyses into poli0981org_pipdock; every npm ci runs with --ignore-scripts (S6505). - Every repository URL points at the organization. README's attestation command for 1.4.0/1.5.0 had stopped working; it now says --owner poli0981 --signer-repo poli0981/pipdock. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
48 lines
1.7 KiB
TOML
48 lines
1.7 KiB
TOML
[package]
|
|
name = "pipdock-core"
|
|
description = "Domain logic for PipDock: engine adapters, planning, snapshots, dependency graph."
|
|
version.workspace = true
|
|
edition.workspace = true
|
|
rust-version.workspace = true
|
|
license.workspace = true
|
|
publish.workspace = true
|
|
repository.workspace = true
|
|
authors.workspace = true
|
|
|
|
[lints]
|
|
workspace = true
|
|
|
|
[features]
|
|
# `fixtures.rs`: the L3 payloads xtask writes for the frontend's tests.
|
|
fixtures = []
|
|
|
|
[dependencies]
|
|
async-trait = "0.1.92"
|
|
jiff = { version = "0.2.38", features = ["serde"] }
|
|
nucleo = "0.5.0"
|
|
reqwest = { version = "0.13.5", default-features = false, features = ["rustls", "http2", "json", "gzip", "charset"] }
|
|
rusqlite = { version = "0.42.0", features = ["bundled"] }
|
|
schemars = "1.2.3"
|
|
serde = { version = "1.0.229", features = ["derive"] }
|
|
serde_json = "1.0.154"
|
|
sha2 = "0.11.1"
|
|
thiserror = "2.0.21"
|
|
# `fs`: an async fn that touches a file goes through tokio's pool rather than blocking a runtime
|
|
# worker (SonarQube rust:S7493).
|
|
tokio = { version = "1.53.3", features = ["rt-multi-thread", "macros", "process", "io-util", "time", "sync", "fs"] }
|
|
# First-party tokio, for CancellationToken. The alternative was an AtomicBool plus a Notify,
|
|
# which is what CancellationToken already is, written worse.
|
|
tokio-util = "0.7.20"
|
|
tracing = "0.1.44"
|
|
|
|
[dev-dependencies]
|
|
jiff = "0.2.38"
|
|
tokio = { version = "1.53.3", features = ["rt-multi-thread", "macros"] }
|
|
|
|
[target."cfg(windows)".dependencies]
|
|
winreg = "0.56.0"
|
|
# Cancelling a build has to reach the compilers `python -m pip` spawns, not just pip itself, and
|
|
# on Windows that means a Job Object. A safe wrapper rather than hand-written unsafe, because
|
|
# `unsafe_code = "forbid"` in the workspace lints is absolute and worth keeping that way.
|
|
win32job = "2.0.3"
|