Files
pipdock/src-tauri/Cargo.toml
T
poli0981andClaude Opus 5.5 12bf723daa ci: failures reach someone, audits run on what is merged, releases are attested
- notify-ci-failure.yml lists its workflows by name. `workflows: ['*']` is not a wildcard to
  workflow_run: it matched nothing, so `main` was red from 2026-09-23 with no one told.
- cargo audit runs a prebuilt cargo-audit (taiki-e/install-action, pinned by commit) with
  `--deny warnings`, replacing rustsec/audit-check@v2 - Node 20, a check-run write token, and on a
  pull request a failure only for "critical", which is how September's advisories passed every PR.
  .cargo/audit.toml's contract (a new informational advisory fails CI) is now what runs.
- security-scan.yml: both audits daily against `main`, so an advisory against something already
  merged is reported the day it is published, not at the next PR.
- cargo deny (licences, sources, bans) with deny.toml: the licence allowlist makes "every bundled
  licence is GPL-3.0-compatible" a test. The workspace declares `publish = false`, which it never
  had - and without which cargo-deny judged the app crates as published ones.
- CodeQL analyses rust and actions as well as javascript-typescript. The comment saying CodeQL had
  no Rust support stopped being true in 2025.
- ci-node.yml: Pages and id-token write move from the workflow to the one job that needs them
  (Sonar S8233); the audit installs with --ignore-scripts (S6505); a new `tauri lockstep` job
  fails when a Tauri crate and its npm package drift apart on Cargo.lock and package-lock.json.
- release.yml: build (read-only token, no persisted credentials) and publish (attest + draft) are
  separate jobs; the tag must match all five version fields; SHA256SUMS.txt is LF, which
  `sha256sum -c` elsewhere needs; actions/attest-build-provenance attests the .exe and .msi;
  softprops/action-gh-release is pinned by commit; `workflow_dispatch` with `dry_run` builds any
  ref without attesting or drafting.
- ci-integration.yml also runs for the CLI, exec, audit, release metadata, errors, store, index,
  Cargo.lock and rust-toolchain.toml - every one of which its end-to-end steps run through.
- dependabot.yml: cooldowns, a group per ecosystem for Tauri packages and for actions and pip,
  TypeScript held below 6.1 (typescript-eslint's peer range), and the rust-toolchain ecosystem.
  A multi-ecosystem group would put both Tauri halves in one PR, but what it does to dependencies
  outside its patterns is undocumented; the lockstep job covers the gap instead.
- Sonar: NOSONAR with reasons on the dev scripts' argv and PATH lookups; bundle-cli.mjs no longer
  claims to run from beforeBuildCommand. The dev CSP moves out of index.html into a Vite plugin
  that reads devCsp from tauri.conf.json, so a release build carries one policy, the strict one
  (S7039); checked in the dev server, where React Refresh's preamble still runs.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-17 00:55:27 +07:00

52 lines
2.1 KiB
TOML

[package]
name = "pipdock-app"
description = "PipDock — Tauri shell. Commands and events only; all logic lives in pipdock-core."
version.workspace = true
edition.workspace = true
rust-version.workspace = true
license.workspace = true
publish.workspace = true
repository.workspace = true
authors.workspace = true
[lib]
name = "pipdock_app_lib"
crate-type = ["staticlib", "cdylib", "rlib"]
[lints]
workspace = true
[build-dependencies]
tauri-build = { version = "2.7.3", features = [] }
[dependencies]
pipdock-core = { path = "../crates/pipdock-core" }
tauri = { version = "2.12.4", features = [] }
tauri-plugin-dialog = "2.8.3"
# Scoped in capabilities/external-links.json: the legal gate and the bug-report deep
# link hand a URL to the browser, because the CSP forbids the webview fetching it.
tauri-plugin-opener = "2.7.2"
# Write-only, for "Copy full log" (ERROR-CATALOG §4).
tauri-plugin-clipboard-manager = "2.5.0"
serde = { version = "1.0.229", features = ["derive"] }
serde_json = "1.0.154"
jiff = "0.2.38"
tokio = { version = "1.53.3", features = ["rt-multi-thread", "sync"] }
# `plan_cancel` trips the same `CancellationToken` the core threads through `exec`.
tokio-util = "0.7.20"
tracing = "0.1.44"
# One window, always. Launching PipDock again focuses the window that exists rather than opening
# a second one — two of them would be two `Sessions` slots over one set of environments, each
# certain it owned the mutation in flight.
tauri-plugin-single-instance = "2.5.4"
tracing-subscriber = { version = "0.3.23", features = ["env-filter"] }
# The one dialog that has to work before Tauri does: the data folder could not be opened, so there
# is no app to show anything in. Already in the tree through tauri-plugin-dialog, with its features.
rfd = { version = "0.16", default-features = false, features = ["common-controls-v6"] }
[dev-dependencies]
# `Sessions` is the one thing in this crate with a protocol worth testing on its own, and every
# method on it is async. The runtime is already a dependency; `macros` and `rt` are what
# `#[tokio::test]` needs on top.
tokio = { version = "1.53.3", features = ["macros", "rt"] }