chore: move to poli0981org — self-contained CI, Qodana, an npm licence gate, this week's dependencies (#119)

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>
This commit is contained in:
poli0981andClaude Opus 5.5 authored and GitHub committed 2026-11-21 21:50:41 +07:00
1 parent efee3ca8d9
commit ccae96dbeb
54 files changed
+5711 -999

No files matched your search

+9
View File
@@ -45,6 +45,15 @@ ignore = [
"RUSTSEC-2026-0371", # zbus_names — unmaintained, merged into zbus 6
"RUSTSEC-2026-0372", # zvariant_derive — unmaintained, merged into zbus 6
# --- chrono, listed and never compiled ----------------------------------
# Cargo.lock names chrono only because serde_with 3.24's `std` feature carries the weak
# features `chrono_0_4?/clock` and `chrono_0_4?/std`, and Cargo's lock resolution records an
# optional dependency that a weak feature mentions even when nothing enables it. serde_with
# comes in through tauri-utils; `cargo tree -i chrono --target all` prints nothing, so no
# target — the shipped Windows one included — compiles it. PipDock's own dates are jiff, the
# advisory's first recommendation. Delete this line when Cargo.lock stops listing chrono.
"RUSTSEC-2026-0543", # chrono — unmaintained
# --- unic-* Unicode tables ----------------------------------------------
# Superseded upstream but functionally frozen data tables, reached transitively. Nothing here
# parses untrusted input on PipDock's behalf.
+2 -2
View File
@@ -4,8 +4,8 @@ blank_issues_enabled: false
contact_links:
- name: Question or idea
url: https://github.com/poli0981/pipdock/discussions
url: https://github.com/poli0981org/pipdock/discussions
about: Ask about usage, propose a feature, or share a workflow.
- name: Security vulnerability
url: https://github.com/poli0981/pipdock/security/advisories/new
url: https://github.com/poli0981org/pipdock/security/advisories/new
about: Report privately via GitHub Security Advisories. Please do not open a public issue.
+2 -2
View File
@@ -4,13 +4,13 @@
The latest release gets fixes. The previous minor gets security-only patches for 90 days. There is
no update channel — PipDock does not update itself, so a fix reaches you when you download the new
build from [Releases](https://github.com/poli0981/pipdock/releases).
build from [Releases](https://github.com/poli0981org/pipdock/releases).
## Reporting a vulnerability
**Do not open a public issue.** Use either:
- [GitHub Security Advisories](https://github.com/poli0981/pipdock/security/advisories/new) — preferred
- [GitHub Security Advisories](https://github.com/poli0981org/pipdock/security/advisories/new) — preferred
- `code@poli0981.dev`
Target acknowledgment is 7 days. Coordinated disclosure is preferred; tell us if you have a
+19 -8
View File
@@ -1,8 +1,7 @@
# Dependency updates — docs/RELEASE-CI.md §2.
#
# Dependabot, not Renovate: there is no Renovate configuration anywhere in the poli0981/.github
# ops repo, and that repo ships a dependabot-summary.yml, which makes Dependabot the portfolio
# standard.
# Dependabot, not Renovate: Dependabot was the standard of the owner's ops repo when the CI was
# set up, and it still is across the poli0981org organization.
#
# Weekly grouped PRs per ecosystem, with Code Health's pins kept apart so a tool bump is reviewed
# on its own. Security advisories bypass grouping and schedule — that is Dependabot's default for
@@ -19,6 +18,13 @@
# its Tauri packages into one PR, and ci-node.yml's `tauri lockstep` job fails either PR until its
# counterpart is merged beside it.
#
# **A group's position decides nothing.** Dependabot gives a dependency to the *most specific*
# group that matches it, and a group with `update-types` counts as more specific than one with
# patterns alone: on 2026-11-21 its log read "Skipping tauri-plugin-dialog for group 'tauri' -
# belongs to more specific group 'cargo-minor-patch'", and every Tauri bump of that week (#116,
# #118) landed in the catch-all groups. This file said the order kept them out. What does is
# `exclude-patterns` on each catch-all, below.
#
# The labels below must exist in the repository, or Dependabot opens its PRs without them.
version: 2
@@ -33,16 +39,20 @@ updates:
cooldown:
default-days: 3
semver-major-days: 14
# No cargo ignores. The rfd one (`>=0.17.0`) went on 2026-11-04: src-tauri takes rfd only
# because tauri-plugin-dialog already compiles it, and 2.8.4 moved that to rfd ^0.17, which
# met the ignore's own condition. If tauri-plugin-dialog moves rfd again, bump both together —
# `cargo tree -i rfd --target all` must still show one rfd.
ignore:
# src-tauri takes rfd only because tauri-plugin-dialog already compiles it, and 2.8.4 — the
# newest — still requires rfd ^0.17, so rfd 0.18 alone (#112) would put a second rfd in the
# binary. Remove this when tauri-plugin-dialog moves to rfd 0.18, and bump both together:
# `cargo tree -i rfd --target all` must still show one rfd. (The same ignore, at 0.17, went
# on 2026-11-04 when its own condition was met.)
- dependency-name: rfd
versions: ['>=0.18.0']
groups:
# First, so a Tauri crate never lands in the catch-all group below.
tauri:
patterns: ['tauri', 'tauri-*']
cargo-minor-patch:
update-types: [minor, patch]
exclude-patterns: ['tauri', 'tauri-*']
labels: [dependencies, rust]
- package-ecosystem: npm
@@ -69,6 +79,7 @@ updates:
patterns: ['vitest', '@vitest/*']
npm-minor-patch:
update-types: [minor, patch]
exclude-patterns: ['@tauri-apps/*', 'vitest', '@vitest/*']
labels: [dependencies, frontend]
- package-ecosystem: github-actions
+164
View File
@@ -0,0 +1,164 @@
#!/usr/bin/env python3
"""Post PipDock's release announcements and CI-failure alerts to Discord webhooks.
Vendored on 2026-11-21, when the repository moved to the poli0981org organization: until then the
notifier was a reusable workflow in the owner's personal ops repo (`poli0981/.github`), which checked
out that repo's `main` and ran *its* copy of a script like this one with PipDock's webhooks in the
environment. A project in the organization no longer runs code another account can change, so the
script lives here — adapted from OmniDeck's self-contained notifier.
Standard library only, so the workflow needs no setup step. Every input comes from environment
variables set by `notify.yml`, never from `${{ }}` interpolated into a shell:
release GITHUB_REPOSITORY, GH_TOKEN, TAG, DISCORD_WEBHOOK, DISCORD_WEBHOOK_EXTRA (optional)
failure GITHUB_REPOSITORY, WORKFLOW_NAME, RUN_URL, BRANCH, COMMIT_SHA, COMMIT_MESSAGE, ACTOR,
EVENT, DISCORD_WEBHOOK
A missing webhook (a fork, or a secret not set) is a notice, not a failure. DRY_RUN=1 prints the
payload instead of posting it, which is how the script is checked without telling Discord anything.
"""
from __future__ import annotations
import json
import os
import sys
import urllib.error
import urllib.parse
import urllib.request
COLOR_RELEASE = 0x57F287 # green
COLOR_PRERELEASE = 0xFEE75C # yellow
COLOR_FAILURE = 0xED4245 # red
# Discord's edge rejects Python's default user agent.
USER_AGENT = "PipDock-notify (+https://github.com/poli0981org/pipdock)"
# The release's downloads, in the order a reader wants them: the installer most people need, the
# MSI for managed deployment, and the checksums both are verified against.
ASSET_SUFFIXES = ("_x64-setup.exe", "_x64_en-US.msi", "SHA256SUMS.txt")
def env(name: str) -> str:
return os.environ.get(name, "").strip()
def truncate(text: str, limit: int) -> str:
return text if len(text) <= limit else text[: limit - 1].rstrip() + "…"
def compact(embed: dict) -> dict:
return {key: value for key, value in embed.items() if value}
def get_release(repository: str, tag: str, token: str) -> dict:
url = f"https://api.github.com/repos/{repository}/releases/tags/{urllib.parse.quote(tag, safe='')}"
headers = {
"Accept": "application/vnd.github+json",
"User-Agent": USER_AGENT,
"X-GitHub-Api-Version": "2022-11-28",
}
if token:
headers["Authorization"] = f"Bearer {token}"
with urllib.request.urlopen(urllib.request.Request(url, headers=headers), timeout=20) as response:
return json.load(response)
def downloads(assets: list[dict]) -> str:
lines = []
for suffix in ASSET_SUFFIXES:
asset = next((a for a in assets if a.get("name", "").endswith(suffix)), None)
if asset:
lines.append(f"[{asset['name']}]({asset['browser_download_url']})")
return "\n".join(lines)
def release_payload() -> dict:
repository, tag = env("GITHUB_REPOSITORY"), env("TAG")
if not tag:
raise ValueError("TAG is empty")
release = get_release(repository, tag, env("GH_TOKEN"))
prerelease = bool(release.get("prerelease"))
fields = [{"name": "Type", "value": "Pre-release" if prerelease else "Stable", "inline": True}]
files = downloads(release.get("assets") or [])
if files:
fields.append({"name": "Downloads", "value": files, "inline": False})
embed = {
"title": f"PipDock {tag}" + (" (pre-release)" if prerelease else ""),
"url": release.get("html_url"),
"description": truncate(release.get("body") or "", 1500),
"color": COLOR_PRERELEASE if prerelease else COLOR_RELEASE,
"fields": fields,
"footer": {"text": repository},
"timestamp": release.get("published_at"),
}
return {"username": "Release Bot", "embeds": [compact(embed)]}
def failure_payload() -> dict:
repository, sha = env("GITHUB_REPOSITORY"), env("COMMIT_SHA")
message_lines = env("COMMIT_MESSAGE").splitlines()
commit = f"[{sha[:7]}](https://github.com/{repository}/commit/{sha})" if sha else "?"
embed = {
"title": f"{env('WORKFLOW_NAME') or 'Workflow'} failed: {repository}",
"url": env("RUN_URL"),
"description": truncate(message_lines[0], 300) if message_lines else "",
"color": COLOR_FAILURE,
"fields": [
{"name": "Ref", "value": env("BRANCH") or "?", "inline": True},
{"name": "Event", "value": env("EVENT") or "?", "inline": True},
{"name": "Commit", "value": commit, "inline": True},
{"name": "Actor", "value": env("ACTOR") or "?", "inline": True},
],
"footer": {"text": repository},
}
return {"username": "CI Bot", "embeds": [compact(embed)]}
def post(webhook: str, payload: dict) -> None:
request = urllib.request.Request(
webhook,
data=json.dumps(payload).encode("utf-8"),
headers={"Content-Type": "application/json", "User-Agent": USER_AGENT},
method="POST",
)
with urllib.request.urlopen(request, timeout=20):
pass # urlopen raises HTTPError for any non-2xx answer
def webhooks(kind: str) -> list[str]:
hooks = [env("DISCORD_WEBHOOK")]
if kind == "release":
# The releases channel and the repository's own channel both hear about a release, as they
# did under the ops-repo announcer.
hooks.append(env("DISCORD_WEBHOOK_EXTRA"))
return [hook for hook in hooks if hook]
def main(argv: list[str]) -> int:
if len(argv) != 2 or argv[1] not in ("release", "failure"):
print("usage: discord_notify.py release|failure", file=sys.stderr)
return 2
kind = argv[1]
targets = webhooks(kind)
dry_run = env("DRY_RUN") == "1"
if not targets and not dry_run:
print("::notice::No Discord webhook is available to this run; nothing was posted.")
return 0
try:
payload = release_payload() if kind == "release" else failure_payload()
if dry_run:
print(json.dumps(payload, indent=2, ensure_ascii=False))
return 0
for target in targets:
post(target, payload)
except (urllib.error.URLError, ValueError, KeyError) as error:
# Never print a webhook URL: it is a secret.
print(f"::error::Discord {kind} notification failed: {error}")
return 1
print(f"Posted the {kind} notification to {len(targets)} Discord webhook(s).")
return 0
if __name__ == "__main__":
sys.exit(main(sys.argv))
-28
View File
@@ -1,28 +0,0 @@
# Caller into the ops repo's Discord announcer.
#
# docs/RELEASE-CI.md §1 originally described a `notify.yml` cross-posting to six platforms; the
# ops repo has no such workflow. Announcements are Discord-only, via
# poli0981/.github/.github/scripts/discord_notify.py.
name: Announce Release
on:
release:
types: [published]
workflow_dispatch:
inputs:
tag:
description: Tag to announce (for re-runs)
required: true
type: string
permissions:
contents: read
actions: read
jobs:
announce:
uses: poli0981/.github/.github/workflows/announce-release.yml@main
with:
tag_override: ${{ inputs.tag || '' }}
secrets: inherit
+6 -6
View File
@@ -81,12 +81,12 @@ jobs:
python: ['3.10', '3.14']
steps:
- name: Checkout
uses: actions/checkout@v7
uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7.0.1
with:
persist-credentials: false
- name: Setup Python ${{ matrix.python }}
uses: actions/setup-python@v7
uses: actions/setup-python@6d4fd22b20465ccc0f7354476588e8df7c9ca0e0 # v7.1.0
with:
python-version: ${{ matrix.python }}
@@ -100,7 +100,7 @@ jobs:
shell: pwsh
- name: Cache cargo
uses: actions/cache@v6
uses: actions/cache@55cc8345863c7cc4c66a329aec7e433d2d1c52a9 # v6.1.0
with:
path: |
~/.cargo/registry
@@ -400,7 +400,7 @@ jobs:
timeout-minutes: 30
steps:
- name: Checkout
uses: actions/checkout@v7
uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7.0.1
with:
persist-credentials: false
@@ -408,7 +408,7 @@ jobs:
# Python 3.12.x environment", so a floating `3.12` turns every runner-image Python bump into
# a fixture diff that says nothing about pip or uv. Bump it deliberately, and re-capture.
- name: Setup Python
uses: actions/setup-python@v7
uses: actions/setup-python@6d4fd22b20465ccc0f7354476588e8df7c9ca0e0 # v7.1.0
with:
python-version: '3.12.10'
@@ -429,7 +429,7 @@ jobs:
# (another interpreter, another network, another day's index).
- name: Upload the captured fixtures
if: always()
uses: actions/upload-artifact@v7
uses: actions/upload-artifact@cf430e030ddbb5b0abf93d22962f4752f3646cd9 # v7.0.2
with:
name: captured-fixtures
path: |
+69 -22
View File
@@ -1,11 +1,15 @@
# Caller into the ops repo's React reusable, plus local jobs.
# The frontend's checks, all project-local.
#
# The reusable runs Node 24, `npm ci`, then lint / typecheck / test when the matching npm script
# exists, then the build. It has no `npm audit` step, so that gate lives here — see
# docs/RELEASE-CI.md §1.
# Until the move to poli0981org (2026-11-21) the `lint · typecheck · test · build` job was a caller
# into the owner's personal ops repo — `poli0981/.github`'s reusable-web-react.yml, at `@main`,
# unpinned. A project in the organization no longer runs a workflow another account can change, so
# the job's steps live here, pinned like every other action in this repository. Two things went
# with the reusable: the `pages: write` and `id-token: write` grants its always-skipped Pages job
# forced on the caller, and the `dist` artifact nothing downloaded.
#
# It also has no working-directory input, which is why package.json sits at the repo root with
# Vite configured `root: './ui'` (ARCHITECTURE §2).
# package.json still sits at the repository root with Vite's `root: './ui'` (ARCHITECTURE §2). The
# reusable's missing `working-directory` input was the original reason and is gone; SonarCloud,
# Qodana, the scripts below and Tauri's own configuration all assume the root now.
name: CI / Node
@@ -23,22 +27,40 @@ concurrency:
jobs:
web:
# A required check under exactly this name (RELEASE-CI.md §2): renaming it means changing the
# branch protection payload in the same breath.
name: lint · typecheck · test · build
# The reusable declares a Pages-deploy job needing `pages: write` and `id-token: write`. It is
# skipped here (`deploy-pages: false`), but permissions are validated at startup regardless of
# `if:`, so a caller that grants less than the callee declares is rejected before it runs.
# Granted on this job only, not the workflow: the other jobs here never need to write.
permissions:
contents: read
pages: write
id-token: write
uses: poli0981/.github/.github/workflows/reusable-web-react.yml@main
runs-on: ubuntu-latest
timeout-minutes: 20
steps:
- name: Checkout
uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7.0.1
with:
persist-credentials: false
- name: Setup Node.js
uses: actions/setup-node@949feb2413d6458794dcd2491c4babbbce0c15c1 # v7.1.0
with:
node-version: '26'
package-manager: npm
build-command: npm run build
dist-dir: dist
deploy-pages: false
cache: npm
# No install script runs: the only package in the lockfile that has one is fsevents, which
# is macOS-only, and a lifecycle script is how a compromised dependency runs on the runner
# (SonarCloud githubactions:S6505). `npm licences` and `npm audit` never needed them either.
- name: Install
run: npm ci --ignore-scripts
- name: Lint
run: npm run lint
- name: Typecheck
run: npm run typecheck
- name: Test
run: npm test
- name: Build
run: npm run build
audit:
name: npm audit
@@ -46,12 +68,12 @@ jobs:
timeout-minutes: 10
steps:
- name: Checkout
uses: actions/checkout@v7
uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7.0.1
with:
persist-credentials: false
- name: Setup Node.js
uses: actions/setup-node@v7
uses: actions/setup-node@949feb2413d6458794dcd2491c4babbbce0c15c1 # v7.1.0
with:
node-version: '26'
cache: npm
@@ -63,13 +85,38 @@ jobs:
- name: Audit
run: npm audit --audit-level=high
licences:
# The npm half of what deny.toml does for the crates: every package the production build can
# bundle must carry a GPL-3.0-compatible licence (THIRD-PARTY-NOTICES, SECURITY §7). It reads
# package-lock.json and installs nothing.
name: npm licences
runs-on: ubuntu-latest
timeout-minutes: 5
steps:
- name: Checkout
uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7.0.1
with:
persist-credentials: false
- name: Setup Node.js
uses: actions/setup-node@949feb2413d6458794dcd2491c4babbbce0c15c1 # v7.1.0
with:
node-version: '26'
# The checker tests itself with Node's built-in runner, so it needs no dependency either.
- name: Test the checker
run: node --test scripts/*.test.mjs
- name: Production dependencies under GPL-3.0-compatible licences
run: node scripts/check-licenses.mjs
lockstep:
name: tauri lockstep
runs-on: ubuntu-latest
timeout-minutes: 5
steps:
- name: Checkout
uses: actions/checkout@v7
uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7.0.1
with:
persist-credentials: false
+7 -8
View File
@@ -1,5 +1,4 @@
# Project-local: the ops repo (poli0981/.github) has no reusable Rust workflow, and only its
# desktop-csharp reusable runs on Windows. See docs/RELEASE-CI.md §1.
# Project-local, like every workflow here since the move to poli0981org (RELEASE-CI.md §1).
#
# Windows runner because the environment-discovery module reads the PEP 514 registry and the `py`
# launcher — a Linux run would skip exactly the code most likely to break.
@@ -29,7 +28,7 @@ jobs:
timeout-minutes: 45
steps:
- name: Checkout
uses: actions/checkout@v7
uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7.0.1
with:
persist-credentials: false
@@ -41,7 +40,7 @@ jobs:
cargo --version
- name: Cache cargo
uses: actions/cache@v6
uses: actions/cache@55cc8345863c7cc4c66a329aec7e433d2d1c52a9 # v6.1.0
with:
path: |
~/.cargo/registry
@@ -70,7 +69,7 @@ jobs:
RUSTUP_TOOLCHAIN: stable
steps:
- name: Checkout
uses: actions/checkout@v7
uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7.0.1
with:
persist-credentials: false
@@ -78,7 +77,7 @@ jobs:
# on Node 20, needed a check-run write token, and on a pull request failed only on
# "critical" — so the advisories that turned `main` red in September passed every PR.
- name: Install cargo-audit
uses: taiki-e/install-action@b80e2bb2635f28eb98b9fce1e2f0887e1535c6b2 # v2.90.0
uses: taiki-e/install-action@4a76afe23f9e08d2d9550fb56e556444e8611d21 # v2.90.4
with:
tool: cargo-audit
@@ -96,12 +95,12 @@ jobs:
RUSTUP_TOOLCHAIN: stable
steps:
- name: Checkout
uses: actions/checkout@v7
uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7.0.1
with:
persist-credentials: false
- name: Install cargo-deny
uses: taiki-e/install-action@b80e2bb2635f28eb98b9fce1e2f0887e1535c6b2 # v2.90.0
uses: taiki-e/install-action@4a76afe23f9e08d2d9550fb56e556444e8611d21 # v2.90.4
with:
tool: cargo-deny
+40 -18
View File
@@ -1,14 +1,18 @@
# Caller into the ops repo's CodeQL reusable.
# CodeQL, project-local since the move to poli0981org (2026-11-21).
#
# Three languages. **Rust** — CodeQL analyses it without a build (`build-mode: none`, which the
# reusable passes for every language outside its autobuild list); this file said for six releases
# that CodeQL had no Rust support, which stopped being true in 2025. **Actions** — the workflows
# themselves: the class of mistake SonarCloud kept finding by hand (write permissions at workflow
# level, unpinned third-party actions). **JavaScript/TypeScript** — the frontend, and the one
# whose check name `main`'s protection requires, so it keeps its exact name.
# It was a caller into the owner's personal ops repo (`poli0981/.github`'s reusable-codeql.yml, at
# `@main`), whose steps used `github/codeql-action@v4` by tag. The same analysis runs here with the
# action pinned by commit, and the write permission on the one job that uploads.
#
# The reusable notes that repo Settings → Advanced Security → CodeQL "Default setup" must be
# DISABLED, or this advanced-setup workflow is rejected at upload time.
# Three languages, all `build-mode: none`. **Rust** — CodeQL analyses it without a build; this
# file said for six releases that CodeQL had no Rust support, which stopped being true in 2025.
# **Actions** — the workflows themselves: write permissions at workflow level, unpinned
# third-party actions, untrusted input in a `run:`. **JavaScript/TypeScript** — the frontend, and
# a required check under exactly the name `Analyze (javascript-typescript)` (RELEASE-CI.md §2).
# The `category` values are the reusable's, so existing alerts keep their history.
#
# Settings → Advanced Security → CodeQL "Default setup" must stay disabled, or this advanced
# setup is rejected at upload time.
name: CodeQL
@@ -20,18 +24,36 @@ on:
# Weekly, offset off the hour to avoid the top-of-hour scheduling pileup.
- cron: '37 4 * * 1'
# A caller cannot grant a called workflow less than its jobs declare, or the run is rejected before
# it starts. reusable-codeql.yml's analyze job asks for `packages: read` to fetch internal CodeQL
# packs, so omitting it here produced a startup_failure with no logs to explain it — the same
# permissions trap RELEASE-CI.md §1 records, from the other direction.
permissions:
actions: read
contents: read
packages: read
security-events: write
jobs:
analyze:
uses: poli0981/.github/.github/workflows/reusable-codeql.yml@main
name: Analyze (${{ matrix.language }})
runs-on: ubuntu-latest
timeout-minutes: 60
permissions:
actions: read
contents: read
packages: read # CodeQL's own query packs
security-events: write # upload the results
strategy:
fail-fast: false
matrix:
language: [javascript-typescript, rust, actions]
steps:
- name: Checkout
uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7.0.1
with:
languages: '["javascript-typescript", "rust", "actions"]'
persist-credentials: false
- name: Initialize CodeQL
uses: github/codeql-action/init@33d7b85da1a04171e211befe2c739303b9a4c066 # v4.39.3
with:
languages: ${{ matrix.language }}
build-mode: none
- name: Perform CodeQL analysis
uses: github/codeql-action/analyze@33d7b85da1a04171e211befe2c739303b9a4c066 # v4.39.3
with:
category: /language:${{ matrix.language }}
-30
View File
@@ -1,30 +0,0 @@
# Caller into the ops repo's Discord CI-failure notifier.
#
# **Listed by name.** `workflows: ['*']`, which the ops repo's own example suggests, is not a
# wildcard to `workflow_run`: it matched nothing, so `main` stayed red from 2026-09-23 with every
# failure unreported — the only runs this ever saw were Dependabot's. Adding a workflow means
# adding its `name:` here, exactly.
#
# CodeQL and Release are deliberately absent: the reusable skips workflows with dedicated
# notifiers by name ('odeQL', 'elease', …), so listing them would only create skipped runs.
name: Notify CI Failure
on:
workflow_run:
workflows:
- CI / Rust
- CI / Node
- CI / Integration
- Security scan
- SonarCloud
types: [completed]
permissions:
contents: read
actions: read
jobs:
notify:
uses: poli0981/.github/.github/workflows/notify-ci-failure.yml@main
secrets: inherit
+92
View File
@@ -0,0 +1,92 @@
# Discord notifications, self-contained in this repository since the move to poli0981org
# (2026-11-21). They were two callers into the owner's personal ops repo, whose notifier checked
# out *that* repo's `main` and ran its script with PipDock's webhooks in the environment; the
# script is vendored now (.github/scripts/discord_notify.py, standard library only).
#
# - ci-failure: a run of a listed workflow failed outside a pull request — a push to `main`, the
# daily or weekly schedule, a dispatch, a release tag -> DISCORD_CI_WEBHOOK. Pull-request runs
# report on the pull request, and a fork's or Dependabot's get no secrets anyway. The filter is
# on the event alone, never on a branch name or a login, which a fork controls.
# - announce: a release was published, or re-announced with a dispatch -> DISCORD_RELEASES_WEBHOOK
# and DISCORD_REPO_WEBHOOK. Publishing the draft (RELEASE-CI.md §3) is done with a person's token,
# which does fire `release: published`; a release published with GITHUB_TOKEN would not.
#
# **The list is by exact `name:`.** `workflows: ['*']`, which the ops repo's own example
# suggested, is not a wildcard to `workflow_run`: it matched nothing, and `main` was red for three
# weeks in September with nobody told. A new workflow is added here by name. Unlike the ops-repo
# reusable, which skipped anything named like CodeQL or Release because they had "dedicated
# notifiers" PipDock never had, CodeQL, Qodana and Release are listed: a failed Release run used
# to reach no channel at all.
name: Notify
on:
workflow_run:
workflows:
- CI / Rust
- CI / Node
- CI / Integration
- CodeQL
- Qodana
- Release
- Security scan
- SonarCloud
types: [completed]
release:
types: [published]
workflow_dispatch:
inputs:
tag:
description: Release tag to announce again (e.g. v1.6.0)
required: true
type: string
permissions:
contents: read
jobs:
ci-failure:
if: >-
github.event_name == 'workflow_run' &&
github.event.workflow_run.conclusion == 'failure' &&
github.event.workflow_run.event != 'pull_request' &&
github.event.workflow_run.event != 'pull_request_target'
runs-on: ubuntu-latest
timeout-minutes: 5
steps:
- name: Checkout
uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7.0.1
with:
persist-credentials: false
sparse-checkout: .github/scripts
- name: Post the failure to Discord
env:
DISCORD_WEBHOOK: ${{ secrets.DISCORD_CI_WEBHOOK }}
WORKFLOW_NAME: ${{ github.event.workflow_run.name }}
RUN_URL: ${{ github.event.workflow_run.html_url }}
BRANCH: ${{ github.event.workflow_run.head_branch }}
COMMIT_SHA: ${{ github.event.workflow_run.head_sha }}
COMMIT_MESSAGE: ${{ github.event.workflow_run.head_commit.message }}
ACTOR: ${{ github.event.workflow_run.actor.login }}
EVENT: ${{ github.event.workflow_run.event }}
run: python3 .github/scripts/discord_notify.py failure
announce:
if: github.event_name == 'release' || github.event_name == 'workflow_dispatch'
runs-on: ubuntu-latest
timeout-minutes: 5
steps:
- name: Checkout
uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7.0.1
with:
persist-credentials: false
sparse-checkout: .github/scripts
- name: Announce on Discord
env:
GH_TOKEN: ${{ github.token }}
TAG: ${{ github.event.release.tag_name || inputs.tag }}
DISCORD_WEBHOOK: ${{ secrets.DISCORD_RELEASES_WEBHOOK }}
DISCORD_WEBHOOK_EXTRA: ${{ secrets.DISCORD_REPO_WEBHOOK }}
run: python3 .github/scripts/discord_notify.py release
+187
View File
@@ -0,0 +1,187 @@
# JetBrains Qodana, in two parts — added 2026-11-21 with the move to poli0981org.
#
# **A monorepo to Qodana.** The repository holds a Rust workspace and a TypeScript frontend, and
# Qodana Cloud has a project for each, with its own token (QODANA_TOKEN_RUST, QODANA_TOKEN_TS_JS)
# and its own configuration (qodana-rust.yaml, qodana-js.yaml): JetBrains' layout for a monorepo.
# The two jobs below never inspect the same file.
#
# **Rust runs in Docker, TypeScript natively.** qodana-rust has no native mode; it is RustRover in
# a Linux container, so `#[cfg(windows)]` code is invisible to it — clippy, CodeQL and SonarQube
# Cloud, all on Windows, cover that. qodana-js runs on the runner after `npm ci`, so it resolves
# the node_modules the build does, with the Node every other workflow uses.
#
# **No token, no analysis**, the way sonar.yml does it: Dependabot's and a fork's pull requests get
# no repository secrets, so their runs are skipped rather than failed.
#
# **No caches** (`use-caches: false`). The repository's Actions cache is near its 10 GB limit, and
# a Qodana cache — an IDE's indexes, and Cargo's registry inside the container — would evict the
# cargo caches the required checks restore. A run is slower for it, and it is not a required
# check (RELEASE-CI.md §2): a failure on `main` reaches Discord through notify.yml.
#
# **Every run is a full scan, and only a new problem fails it.** `pr-mode` is off: a whole scan is
# two to three minutes a part, so analysing only a pull request's files would save little and make
# a result depend on which files happened to change. `.qodana/rust.sarif.json` is the baseline —
# the 62 problems the first real run found, triaged on 2026-11-21 (ROADMAP: two Critical that are
# RustRover misreading what rustc compiles, and 60 Moderate style findings), trimmed to the results
# and their fingerprints. `--fail-threshold 0` then fails on anything outside it. The TypeScript
# half has no baseline because it has no accepted problem: the six it found were fixed.
#
# **Only new problems reach Code scanning**, under `qodana-rust` and `qodana-js` — a baseline
# problem is triaged already, and alerting on it again would bury the next real one.
name: Qodana
on:
pull_request:
push:
branches: [main]
workflow_dispatch:
permissions:
contents: read
concurrency:
group: qodana-${{ github.ref }}
cancel-in-progress: true
jobs:
tokens:
name: tokens present
runs-on: ubuntu-latest
timeout-minutes: 2
outputs:
rust: ${{ steps.check.outputs.rust }}
js: ${{ steps.check.outputs.js }}
steps:
# `secrets` cannot be read in an `if:`, so presence becomes an output. Only the emptiness test
# sees the values; nothing is checked out and nothing else runs.
- name: Check
id: check
env:
RUST: ${{ secrets.QODANA_TOKEN_RUST }}
JS: ${{ secrets.QODANA_TOKEN_TS_JS }}
run: |
for part in RUST JS; do
name=$(echo "$part" | tr '[:upper:]' '[:lower:]')
if [ -n "${!part}" ]; then
echo "$name=true" >> "$GITHUB_OUTPUT"
else
echo "$name=false" >> "$GITHUB_OUTPUT"
echo "::notice::No Qodana token for the $name part in this run (a Dependabot or fork pull request); it is skipped."
fi
done
rust:
name: qodana · rust
needs: tokens
if: needs.tokens.outputs.rust == 'true'
runs-on: ubuntu-latest
timeout-minutes: 60
permissions:
contents: read
checks: write # annotations
pull-requests: write # the summary comment
security-events: write # new problems to Code scanning
steps:
- name: Checkout
uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7.0.1
with:
# The pull request's own head, and the history pull-request mode diffs against.
ref: ${{ github.event.pull_request.head.sha }}
fetch-depth: 0
persist-credentials: false
- name: Qodana
uses: JetBrains/qodana-action@3e8d76ff0e0241618abd808682f426afe84bab3f # v2026.2.2
env:
QODANA_TOKEN: ${{ secrets.QODANA_TOKEN_RUST }}
# The container runs as the runner's user, and the image's CARGO_HOME (/usr/local/cargo)
# belongs to root, so `cargo metadata` could not write the registry it downloads and
# RustRover loaded no Cargo project — 0 problems from 0 files analysed. /data/cache is
# the container's mount of the action's cache directory, which this user owns.
CARGO_HOME: /data/cache/cargo-home
with:
args: --config qodana-rust.yaml --linter qodana-rust --baseline .qodana/rust.sarif.json --fail-threshold 0
env-vars-to-linter: CARGO_HOME
pr-mode: false
use-caches: false
upload-result: true
artifact-name: qodana-rust
- name: Keep the problems outside the baseline
id: filter
if: ${{ !cancelled() }}
env:
SARIF: ${{ runner.temp }}/qodana/results/qodana.sarif.json
run: |
if [ ! -f "$SARIF" ]; then echo "::notice::The scan left no SARIF."; exit 0; fi
jq '.runs |= map(.results |= map(select((.baselineState // "new") != "unchanged" and (.baselineState // "new") != "absent")))' \
"$SARIF" > "$RUNNER_TEMP/qodana-rust.sarif"
echo "ready=true" >> "$GITHUB_OUTPUT"
- name: Upload to Code scanning
if: ${{ !cancelled() && steps.filter.outputs.ready == 'true' }}
uses: github/codeql-action/upload-sarif@33d7b85da1a04171e211befe2c739303b9a4c066 # v4.39.3
with:
sarif_file: ${{ runner.temp }}/qodana-rust.sarif
category: qodana-rust
js:
name: qodana · ts/js
needs: tokens
if: needs.tokens.outputs.js == 'true'
runs-on: ubuntu-latest
timeout-minutes: 45
permissions:
contents: read
checks: write # annotations
pull-requests: write # the summary comment
security-events: write # new problems to Code scanning
steps:
- name: Checkout
uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7.0.1
with:
ref: ${{ github.event.pull_request.head.sha }}
fetch-depth: 0
persist-credentials: false
- name: Setup Node.js
uses: actions/setup-node@949feb2413d6458794dcd2491c4babbbce0c15c1 # v7.1.0
with:
node-version: '26'
cache: npm
# No install script runs: the only package in the lockfile that has one is fsevents, which
# is macOS-only, and a lifecycle script is how a compromised dependency runs on the runner
# (SonarCloud githubactions:S6505). `npm licences` and `npm audit` never needed them either.
- name: Install
run: npm ci --ignore-scripts
- name: Qodana
uses: JetBrains/qodana-action@3e8d76ff0e0241618abd808682f426afe84bab3f # v2026.2.2
env:
QODANA_TOKEN: ${{ secrets.QODANA_TOKEN_TS_JS }}
with:
args: --config qodana-js.yaml --linter qodana-js --within-docker false --fail-threshold 0
pr-mode: false
use-caches: false
upload-result: true
artifact-name: qodana-js
- name: Keep the problems outside the baseline
id: filter
if: ${{ !cancelled() }}
env:
SARIF: ${{ runner.temp }}/qodana/results/qodana.sarif.json
run: |
if [ ! -f "$SARIF" ]; then echo "::notice::The scan left no SARIF."; exit 0; fi
jq '.runs |= map(.results |= map(select((.baselineState // "new") != "unchanged" and (.baselineState // "new") != "absent")))' \
"$SARIF" > "$RUNNER_TEMP/qodana-js.sarif"
echo "ready=true" >> "$GITHUB_OUTPUT"
- name: Upload to Code scanning
if: ${{ !cancelled() && steps.filter.outputs.ready == 'true' }}
uses: github/codeql-action/upload-sarif@33d7b85da1a04171e211befe2c739303b9a4c066 # v4.39.3
with:
sarif_file: ${{ runner.temp }}/qodana-js.sarif
category: qodana-js
+17 -11
View File
@@ -1,8 +1,8 @@
# Project-local: the ops repo has no reusable Tauri/build workflow (docs/RELEASE-CI.md §1).
# Project-local, like every workflow here (RELEASE-CI.md §1).
#
# Builds the NSIS .exe and .msi, attests where they were built, publishes SHA256SUMS.txt and leaves
# a DRAFT release. Publishing is a separate, human-directed step (RELEASE-CI.md §3.4), and
# announce-release.yml fires on `release: published`.
# notify.yml's announcement fires on `release: published`.
#
# **Two jobs, so the token that can write releases never runs the build.** Building executes
# third-party code — every crate's build script, every npm package's — and gets a read-only token
@@ -54,7 +54,7 @@ jobs:
tag: ${{ steps.version.outputs.tag }}
steps:
- name: Checkout
uses: actions/checkout@v7
uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7.0.1
with:
ref: ${{ inputs.tag || github.ref }}
persist-credentials: false
@@ -92,13 +92,13 @@ jobs:
"tag=v$v" >> $env:GITHUB_OUTPUT
- name: Setup Node.js
uses: actions/setup-node@v7
uses: actions/setup-node@949feb2413d6458794dcd2491c4babbbce0c15c1 # v7.1.0
with:
node-version: '26'
cache: npm
- name: Cache cargo
uses: actions/cache@v6
uses: actions/cache@55cc8345863c7cc4c66a329aec7e433d2d1c52a9 # v6.1.0
with:
path: |
~/.cargo/registry
@@ -107,8 +107,12 @@ jobs:
key: ${{ runner.os }}-cargo-release-${{ hashFiles('**/Cargo.lock', 'rust-toolchain.toml') }}
restore-keys: ${{ runner.os }}-cargo-release-
# No install script runs: the only package in the lockfile that has one is fsevents, which
# is macOS-only, and a lifecycle script is how a compromised dependency runs on the runner
# (SonarCloud githubactions:S6505). The bundle does not need them: Tauri's CLI arrives as
# an optional platform package, not a download in a postinstall.
- name: Install frontend dependencies
run: npm ci
run: npm ci --ignore-scripts
# One script owns the recipe (`package.json` → `bundle`), so the workflow cannot drift
# from what a developer runs locally. It stages the CLI sidecar, then bundles with the
@@ -149,7 +153,7 @@ jobs:
Get-Content release-artifacts\SHA256SUMS.txt
- name: Upload the build
uses: actions/upload-artifact@v7
uses: actions/upload-artifact@cf430e030ddbb5b0abf93d22962f4752f3646cd9 # v7.0.2
with:
name: release-artifacts
path: release-artifacts/*
@@ -167,15 +171,17 @@ jobs:
attestations: write
steps:
- name: Download the build
uses: actions/download-artifact@v8
uses: actions/download-artifact@9000827ccba6bdab643e8b6fd33ac0654aef8333 # v8.0.2
with:
name: release-artifacts
path: release-artifacts
# Build provenance for the two installers: `gh attestation verify <file> --repo
# poli0981/pipdock` proves an installer came from this workflow, at this commit — which a
# poli0981org/pipdock` proves an installer came from this workflow, at this commit — which a
# checksum published beside the file cannot, since whoever could replace one could replace
# both.
# both. An attestation stays with the account that made it: those of 1.4.0 and 1.5.0, made
# before the repository moved to the organization, verify with `--owner poli0981
# --signer-repo poli0981/pipdock` and no longer with any `--repo` (README, Install).
- name: Attest provenance
uses: actions/attest-build-provenance@4d101475d8b20a2381f78447822ac1eab6504dd8 # v4.2.2
with:
@@ -184,7 +190,7 @@ jobs:
release-artifacts/*.msi
- name: Draft GitHub release
uses: softprops/action-gh-release@efb35369e0ad2afab669f228072c1b0d510eae64 # v3.0.3
uses: softprops/action-gh-release@8a0cd651e5b2365bd640854a3fa5dfc70e4875f3 # v3.0.4
with:
tag_name: ${{ needs.build.outputs.tag }}
draft: true # reviewed, then published; publishing triggers the announcement
+4 -4
View File
@@ -28,12 +28,12 @@ jobs:
RUSTUP_TOOLCHAIN: stable
steps:
- name: Checkout
uses: actions/checkout@v7
uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7.0.1
with:
persist-credentials: false
- name: Install cargo-audit
uses: taiki-e/install-action@b80e2bb2635f28eb98b9fce1e2f0887e1535c6b2 # v2.90.0
uses: taiki-e/install-action@4a76afe23f9e08d2d9550fb56e556444e8611d21 # v2.90.4
with:
tool: cargo-audit
@@ -46,12 +46,12 @@ jobs:
timeout-minutes: 10
steps:
- name: Checkout
uses: actions/checkout@v7
uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7.0.1
with:
persist-credentials: false
- name: Setup Node.js
uses: actions/setup-node@v7
uses: actions/setup-node@949feb2413d6458794dcd2491c4babbbce0c15c1 # v7.1.0
with:
node-version: '26'
cache: npm
+9 -6
View File
@@ -74,20 +74,23 @@ jobs:
timeout-minutes: 60
steps:
- name: Checkout
uses: actions/checkout@v7
uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7.0.1
with:
# Full history: new code is decided by blame, and a shallow clone has none to give.
fetch-depth: 0
persist-credentials: false
- name: Setup Node.js
uses: actions/setup-node@v7
uses: actions/setup-node@949feb2413d6458794dcd2491c4babbbce0c15c1 # v7.1.0
with:
node-version: '26'
cache: npm
# No install script runs: the only package in the lockfile that has one is fsevents, which
# is macOS-only, and a lifecycle script is how a compromised dependency runs on the runner
# (SonarCloud githubactions:S6505). `npm licences` and `npm audit` never needed them either.
- name: Install frontend dependencies
run: npm ci
run: npm ci --ignore-scripts
- name: TypeScript coverage
run: npm run test:coverage
@@ -96,7 +99,7 @@ jobs:
# the instrumented build lands in target/llvm-cov-target and is rebuilt every run, because
# saving a fourth multi-GB cargo cache would evict the three the required checks depend on.
- name: Restore cargo cache
uses: actions/cache/restore@v6
uses: actions/cache/restore@55cc8345863c7cc4c66a329aec7e433d2d1c52a9 # v6.1.0
with:
path: |
~/.cargo/registry
@@ -111,7 +114,7 @@ jobs:
run: rustup component add llvm-tools-preview
- name: Install cargo-llvm-cov
uses: taiki-e/install-action@b80e2bb2635f28eb98b9fce1e2f0887e1535c6b2 # v2.90.0
uses: taiki-e/install-action@4a76afe23f9e08d2d9550fb56e556444e8611d21 # v2.90.4
with:
tool: cargo-llvm-cov
@@ -139,7 +142,7 @@ jobs:
"version=$v" >> $env:GITHUB_OUTPUT
- name: Scan
uses: SonarSource/sonarqube-scan-action@e805d875275f728fac1885b413934be6d7c63f65 # v8.4.1
uses: SonarSource/sonarqube-scan-action@59202af334b4ba7b5db01b701b8e79f8b3bef0f4 # v8.5.0
env:
SONAR_TOKEN: ${{ secrets.SONAR_TOKEN }}
with:
File diff suppressed because it is too large. Load diff
+1 -1
View File
@@ -152,7 +152,7 @@ where there is a workaround it is given.
Either of these reaches the same person:
- **[Open an accessibility issue](https://github.com/poli0981/pipdock/issues/new?template=accessibility.yml)**
- **[Open an accessibility issue](https://github.com/poli0981org/pipdock/issues/new?template=accessibility.yml)**
on GitHub, or
- write to **[accessibility@poli0981.dev](mailto:accessibility@poli0981.dev)** — no account needed.
+37 -16
View File
@@ -1,7 +1,7 @@
# PipDock — working notes for Claude
Windows GUI + CLI for bulk-managing Python packages. Tauri 2 + Rust core + React 19.
Repo `poli0981/pipdock` · GPL-3.0-only · **Status: 1.5.0. M1, M2, Phase 3, Phase 4, the P1 wave, the Security tab and the dependency view are all complete.** 1.0.0 shipped the release pipeline, a protected `main`, the manual charter and legal documents that match the code; 1.1.0 added pin auto-suggest, requirements export/import, the cache manager and the `Ctrl+K` palette; 1.2.0 added the Security tab (PRD P1-1); 1.3.0 added the dependency view (P1-6), which is a *mode of the package screen* rather than a tab and adds no runtime dependency — read its ROADMAP record before touching `graph/`, because the shape of the screen is a consequence of measurements rather than of taste. 1.4.0 added no feature: it is the audit release — about 170 findings, every Critical and High fixed with a test that failed first, and the rest in ROADMAP's **Audit backlog**, with file:line and a reason each. Read that table before starting a slice; most of what is wrong with the codebase is already written down there. 1.5.0 added no feature either: it is the accessibility pass (backlog U45, U47, U48) — focus, names, keyboard patterns and high contrast, axe-core in the suite, and `ACCESSIBILITY.md`, which is a *record of what was tested* and has to be kept true like one. **What is left of Post-1.0 is one thing** — the scheduled check (P1-7) — and `docs/ROADMAP.md` now carries the survey of what blocks it, which for two versions it was cited for and did not contain: no toast component, no notification/autostart/tray plugin, nothing on a timer, and no surface that can report a background failure.
Repo `poli0981org/pipdock` (moved from `poli0981/pipdock` on 2026-11-21) · GPL-3.0-only · **Status: 1.5.0. M1, M2, Phase 3, Phase 4, the P1 wave, the Security tab and the dependency view are all complete.** 1.0.0 shipped the release pipeline, a protected `main`, the manual charter and legal documents that match the code; 1.1.0 added pin auto-suggest, requirements export/import, the cache manager and the `Ctrl+K` palette; 1.2.0 added the Security tab (PRD P1-1); 1.3.0 added the dependency view (P1-6), which is a *mode of the package screen* rather than a tab and adds no runtime dependency — read its ROADMAP record before touching `graph/`, because the shape of the screen is a consequence of measurements rather than of taste. 1.4.0 added no feature: it is the audit release — about 170 findings, every Critical and High fixed with a test that failed first, and the rest in ROADMAP's **Audit backlog**, with file:line and a reason each. Read that table before starting a slice; most of what is wrong with the codebase is already written down there. 1.5.0 added no feature either: it is the accessibility pass (backlog U45, U47, U48) — focus, names, keyboard patterns and high contrast, axe-core in the suite, and `ACCESSIBILITY.md`, which is a *record of what was tested* and has to be kept true like one. **What is left of Post-1.0 is one thing** — the scheduled check (P1-7) — and `docs/ROADMAP.md` now carries the survey of what blocks it, which for two versions it was cited for and did not contain: no toast component, no notification/autostart/tray plugin, nothing on a timer, and no surface that can report a background failure.
## Read the docs before changing anything
@@ -64,9 +64,9 @@ failed package never aborts a batch (skip-and-continue, then a `"13 successful,
- Crates `pipdock-*`; React components prefixed `Pd` (`PdPackageRow`, `PdConflictRow`)
- Tauri identifier `com.skullmute.pipdock`; CLI binary `pipdock`
- Frontend lives in `ui/`, but `package.json` sits at the **repo root** so the ops-repo
`reusable-web-react.yml` (which has no `working-directory` input) works unmodified; Vite is
configured with `root: './ui'`
- Frontend lives in `ui/`, but `package.json` sits at the **repo root** — first for the ops
repo's reusable CI workflow, which had no `working-directory` input, and now because SonarCloud,
Qodana, the scripts and Tauri's config all assume it; Vite is configured with `root: './ui'`
- Rust ↔ TS types are generated by `cargo run -p xtask -- bindings` over `schemars` — never
hand-mirror a type. (ARCHITECTURE §9 originally said `specta`/`tauri-specta`; `bindings.rs` records
why it is not, and drift is a `cargo test` failure rather than a compile error)
@@ -74,24 +74,45 @@ failed package never aborts a batch (skip-and-continue, then a `"13 successful,
## CI reality
`docs/RELEASE-CI.md` is authoritative *as corrected*: the ops repo `poli0981/.github` has **no
reusable Rust or Tauri workflow**, its notifiers are **Discord-only**, dependency bumps are
**Dependabot** (not Renovate), and its CodeQL reusable *lists* no Rust but passes `languages`
straight to codeql-action, which analyses Rust and Actions without a build — `codeql.yml` asks for
both. So `ci-rust.yml`, `release.yml`, `security-scan.yml` and `sonar.yml` are project-local; `ci-node.yml`,
`codeql.yml` and the notifiers are callers. Every caller needs an explicit `permissions:` block —
callers without one default to `none` — and a write permission belongs on the job that needs it,
not the workflow.
`docs/RELEASE-CI.md` is authoritative. **Every workflow is project-local since 2026-11-21**, when
the repository moved to the poli0981org organization: `ci-node.yml`'s web job, `codeql.yml` and the
Discord notifier were callers into the owner's personal ops repo (`poli0981/.github`, at `@main`)
until then, and a project in the organization no longer runs code another account can change.
**Every action is pinned by commit** with its version in a comment, GitHub's own included, and a
write permission belongs on the job that needs it, not the workflow. Dependency bumps are
**Dependabot** (not Renovate); notifications are **Discord-only**, through the vendored
`.github/scripts/discord_notify.py` (`DRY_RUN=1` prints instead of posting).
**`notify-ci-failure.yml` lists its workflows by name, and a new workflow has to be added to it.**
`workflows: ['*']` — the ops repo's own example — is not a wildcard to `workflow_run`: it matched
**Eight checks are required on `main`** — `fmt · clippy · test`, `cargo audit`, `cargo deny`,
`lint · typecheck · test · build`, `npm audit`, `npm licences`, `tauri lockstep`,
`Analyze (javascript-typescript)` — and a required name is this repository's own now, so renaming a
job means changing the protection payload in the same change (RELEASE-CI §2). `npm licences` is the
npm half of `deny.toml`: `scripts/check-licenses.mjs` with the same allowlist, entry for entry.
**`notify.yml` lists its workflows by name, and a new workflow has to be added to it.**
`workflows: ['*']` — the ops repo's old example — is not a wildcard to `workflow_run`: it matched
nothing, and `main` was red from 2026-09-23 for three weeks with no one told. Start any CI
question with `gh run list --branch main`, and remember that `security-scan.yml` exists for the
case no PR will catch: an advisory against something already merged.
**Dependabot gives a dependency to the *most specific* group, not the first.** A group with
`update-types` beats one with patterns alone, so the `tauri` groups caught nothing until the
catch-alls got `exclude-patterns` (2026-11-21); the order of groups in `dependabot.yml` decides
nothing. Its log says which group took what ("belongs to more specific group").
**Qodana runs as two Qodana Cloud projects** — `qodana-rust.yaml` (RustRover in Docker; it cannot
see `#[cfg(windows)]` code) and `qodana-js.yaml` (WebStorm, native), one token each — and is not a
required check. A new workflow cannot be dispatched before it exists on `main`, so a workflow's
first full run happens in its own PR.
**An attestation stays with the account that made it.** After the transfer, 1.4.0 and 1.5.0 verify
only with `gh attestation verify <file> --owner poli0981 --signer-repo poli0981/pipdock`; every
`--repo` form returns 404 for them. 1.6.0 on verifies with `--repo poli0981org/pipdock`.
**SonarQube Cloud is CI-based since 2026-10-25** — `sonar.yml` and `sonar-project.properties`;
automatic analysis is off in the project's settings and must stay off, or the CI analysis is
refused. Automatic analysis never analysed a line of Rust and imported no coverage, which is why it
since 2026-11-21 the project is `poli0981org_pipdock` in the `poli0981org` organization (the old
`poli0981_pipdock` keeps the history to 1.5.0). Automatic analysis is off in the project's settings
and must stay off, or the CI analysis is refused. Automatic analysis never analysed a line of Rust and imported no coverage, which is why it
went. The gate's "new code" is *previous version*, with the version from `package.json`, and a
bump takes effect **one analysis late**: the analysis that first sent `1.4.0` still measured from
2026-09-27, and the next measured from the last analysis of the version before it (2026-10-20,
+13 -7
View File
@@ -8,12 +8,12 @@ By taking part you agree to the [Code of Conduct](CODE_OF_CONDUCT.md).
## Before you write code
- **A bug** — [open an issue](https://github.com/poli0981/pipdock/issues/new/choose). The in-app
- **A bug** — [open an issue](https://github.com/poli0981org/pipdock/issues/new/choose). The in-app
*Report bug* button fills most of the form in for you.
- **Something that gets in your way as a keyboard, screen-reader or high-contrast user** — see
[ACCESSIBILITY.md](ACCESSIBILITY.md). That report does not need a diagnosis.
- **A security problem** — do not open an issue; follow the [security policy](.github/SECURITY.md).
- **A question or an idea** — [Discussions](https://github.com/poli0981/pipdock/discussions).
- **A question or an idea** — [Discussions](https://github.com/poli0981org/pipdock/discussions).
- **A feature** — please ask first. The design is written down in `docs/`, the feature list and its
non-goals are in [`docs/PRD.md`](docs/PRD.md), and what is planned and why is in
[`docs/ROADMAP.md`](docs/ROADMAP.md). A pull request that contradicts those will be asked to
@@ -68,11 +68,17 @@ cargo clippy --workspace --all-targets --locked -- -D warnings
cargo test --workspace --locked
```
A pull request needs five checks green before it can merge — `fmt · clippy · test`, `cargo audit`,
`lint · typecheck · test · build`, `npm audit` and CodeQL for JavaScript/TypeScript. Several more
run and are read before merging (`cargo deny`, the Tauri version lockstep, CodeQL for Rust and
Actions, the real-engine integration tests, SonarQube Cloud). New code is expected to be covered by
tests; the SonarQube gate asks for 80 % on new lines.
```bash
node scripts/check-licenses.mjs
```
A pull request needs eight checks green before it can merge — `fmt · clippy · test`, `cargo audit`,
`cargo deny`, `lint · typecheck · test · build`, `npm audit`, `npm licences`, `tauri lockstep` and
CodeQL for JavaScript/TypeScript. Several more run and are read before merging (CodeQL for Rust and
Actions, the real-engine integration tests, SonarQube Cloud, Qodana). New code is expected to be
covered by tests; the SonarQube gate asks for 80 % on new lines. A new dependency the app ships must
be under a licence `deny.toml` allows — the two licence checks fail otherwise, and widening the list
is a licensing decision, not a CI fix.
## What a pull request should look like
Generated
+99 -221
View File
@@ -238,7 +238,7 @@ checksum = "4f8abc12baad266b1c8cec146854c195b5864b4221d4b2ca7296a7ae82d9e451"
dependencies = [
"proc-macro2",
"quote",
"syn 3.0.9",
"syn 3.0.10",
]
[[package]]
@@ -273,7 +273,7 @@ checksum = "82f6aeea286b8eb4dd3431a1be1b59d290ace00f5bfd8e2a159bc2a05e2c1667"
dependencies = [
"proc-macro2",
"quote",
"syn 3.0.9",
"syn 3.0.10",
]
[[package]]
@@ -629,14 +629,14 @@ dependencies = [
"iana-time-zone",
"num-traits",
"serde",
"windows-link 0.2.1",
"windows-link",
]
[[package]]
name = "clap"
version = "4.6.7"
version = "4.6.8"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "aa8876b300ab35ba921adea3dfd70157a46249b33f95c9084ae5709785478946"
checksum = "ac230478587d0269d8d6998b82ae69ea51509d55df66d9e92edd1f986904cd4a"
dependencies = [
"clap_builder",
"clap_derive",
@@ -656,14 +656,14 @@ dependencies = [
[[package]]
name = "clap_derive"
version = "4.6.7"
version = "4.6.8"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "f9c751b79415d4e559e3d1fcf128e09e720eb673a06d26cf6f392d37d75b66e0"
checksum = "895c9d8d2ac2dd8b8a29f3724a14e72aaaa6debcf8c38c82f97305c6a172767a"
dependencies = [
"heck 0.5.0",
"proc-macro2",
"quote",
"syn 3.0.9",
"syn 3.0.10",
]
[[package]]
@@ -911,7 +911,7 @@ source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "d045de693cb712d0b22c6a64be5b953f67b3ce00ab5ad3dd5d8b441886ab8e1a"
dependencies = [
"quote",
"syn 3.0.9",
"syn 3.0.10",
]
[[package]]
@@ -940,7 +940,7 @@ dependencies = [
"proc-macro2",
"quote",
"strsim",
"syn 3.0.9",
"syn 3.0.10",
]
[[package]]
@@ -951,7 +951,7 @@ checksum = "2ac7135c3ef02b2f7833bbeb1be5ba7f966dcde8a87c6b87f65a778d71a02785"
dependencies = [
"darling_core",
"quote",
"syn 3.0.9",
"syn 3.0.10",
]
[[package]]
@@ -965,37 +965,6 @@ dependencies = [
"windows-sys 0.61.2",
]
[[package]]
name = "defmt"
version = "1.2.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "e4a0795ac740cb54d7b3775c9c17345f6aaecf884c01733b39d6017738e0e3e1"
dependencies = [
"bitflags 1.3.2",
"defmt-macros",
]
[[package]]
name = "defmt-macros"
version = "1.2.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "840bb056bd99c495c9188198a258ab787c79f306d864db3e6e8451442d6d8366"
dependencies = [
"defmt-parser",
"proc-macro2",
"quote",
"syn 3.0.9",
]
[[package]]
name = "defmt-parser"
version = "1.1.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "71958f69fb2de856c5dd51ac9377e986ca1aa5919f931bf5395a807277f889a0"
dependencies = [
"thiserror 2.0.21",
]
[[package]]
name = "deranged"
version = "0.5.9"
@@ -1094,7 +1063,7 @@ checksum = "c6232dd377dcc64799954cbd3a9bb882e9cdc1308ccd87b1c098f1fb2eaf82a8"
dependencies = [
"proc-macro2",
"quote",
"syn 3.0.9",
"syn 3.0.10",
]
[[package]]
@@ -1405,7 +1374,7 @@ checksum = "ea5190182e6915eb873ddbc16e23b711b6eb1f9c00a0d0a3a91b5f6228475225"
dependencies = [
"proc-macro2",
"quote",
"syn 3.0.9",
"syn 3.0.10",
]
[[package]]
@@ -1482,7 +1451,7 @@ checksum = "9fb9654ba8355388abeb8dcb4fc62f511300867002afc858860463bdd9fe0c44"
dependencies = [
"proc-macro2",
"quote",
"syn 3.0.9",
"syn 3.0.10",
]
[[package]]
@@ -1629,7 +1598,7 @@ source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "1bd49230192a3797a9a4d6abe9b3eed6f7fa4c8a8a4947977c6f80025f92cbd8"
dependencies = [
"rustix",
"windows-link 0.2.1",
"windows-link",
]
[[package]]
@@ -2036,7 +2005,7 @@ dependencies = [
"js-sys",
"log",
"wasm-bindgen",
"windows-core 0.62.2",
"windows-core",
]
[[package]]
@@ -2290,11 +2259,10 @@ dependencies = [
[[package]]
name = "jiff"
version = "0.2.39"
version = "0.2.46"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "3ac703058abac89e5c39b0b879dce2b6b14a4ba36600c7e7e3d0c60a6883ef3c"
checksum = "175dc66334db3b9ab9985bf8b61cfed50dc16d20964bb47f9e479adcae984a7f"
dependencies = [
"defmt",
"jiff-core",
"jiff-static",
"jiff-tzdb-platform",
@@ -2302,24 +2270,23 @@ dependencies = [
"portable-atomic",
"portable-atomic-util",
"serde_core",
"windows-link 0.2.1",
"windows-link",
]
[[package]]
name = "jiff-core"
version = "0.1.2"
version = "0.1.8"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "aee43309eb53bafb8c36d35d6e444769c8f8e6206a9fbf7546f5db9d7d4a0e93"
checksum = "e599b80292e597019b8b3e392de3f4bea2959ddfb8c7dff60e035e9e311a2c1b"
dependencies = [
"defmt",
"log",
]
[[package]]
name = "jiff-static"
version = "0.2.39"
version = "0.2.46"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "6dc32470c67eb7d0e9ccb74303fa925313dc04cecb1aa048beaa6f391e36a93d"
checksum = "c7b1af7547d47354bc438d797e3854601bde8f8d185780c5ba4ab27afa54f1ba"
dependencies = [
"jiff-core",
"proc-macro2",
@@ -2372,7 +2339,7 @@ dependencies = [
"simd_cesu8",
"thiserror 2.0.21",
"walkdir",
"windows-link 0.2.1",
"windows-link",
]
[[package]]
@@ -2535,9 +2502,9 @@ dependencies = [
[[package]]
name = "libsqlite3-sys"
version = "0.39.1"
version = "0.40.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "14a5f01b87b92705d07b433c06f96cbc764637d81a0bffb5734ce17cf0f9a2b3"
checksum = "b06e69070b7e12262b0cd90832f0a7396f142a2b330181255562decf9f0c6215"
dependencies = [
"cc",
"pkg-config",
@@ -3102,7 +3069,7 @@ dependencies = [
"libc",
"redox_syscall",
"smallvec",
"windows-link 0.2.1",
"windows-link",
]
[[package]]
@@ -3617,7 +3584,7 @@ checksum = "92ecd8964f8453721699a1ed72037b0db49ce2f5a5138486ee89bed6f67cdf3a"
dependencies = [
"proc-macro2",
"quote",
"syn 3.0.9",
"syn 3.0.10",
]
[[package]]
@@ -3743,9 +3710,9 @@ dependencies = [
[[package]]
name = "rusqlite"
version = "0.41.1"
version = "0.42.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "da9bba6f3506135e120a6586df05be18b48d18896600646a4bec8f993d91a594"
checksum = "a4edff0039f148731aee2fd80f76dbfeb12d204ab3d1c544838d34e02151049b"
dependencies = [
"bitflags 2.13.2",
"fallible-iterator",
@@ -3944,7 +3911,7 @@ dependencies = [
"proc-macro2",
"quote",
"serde_derive_internals 0.30.0",
"syn 3.0.9",
"syn 3.0.10",
]
[[package]]
@@ -4044,7 +4011,7 @@ checksum = "e7a5d71263a5a7d47b41f6b3f06ba276f10cc18b0931f1799f710578e2309348"
dependencies = [
"proc-macro2",
"quote",
"syn 3.0.9",
"syn 3.0.10",
]
[[package]]
@@ -4066,7 +4033,7 @@ checksum = "f852137cce035d6a4df67ccce505ff6b3e9fd3a10e3e52b24dc71e650bb1a9bd"
dependencies = [
"proc-macro2",
"quote",
"syn 3.0.9",
"syn 3.0.10",
]
[[package]]
@@ -4090,7 +4057,7 @@ checksum = "8d3b1629de253c70a0508c3899572da79ca359fdab27c7920ff00406df418906"
dependencies = [
"proc-macro2",
"quote",
"syn 3.0.9",
"syn 3.0.10",
]
[[package]]
@@ -4141,7 +4108,7 @@ dependencies = [
"darling",
"proc-macro2",
"quote",
"syn 3.0.9",
"syn 3.0.10",
]
[[package]]
@@ -4328,9 +4295,9 @@ dependencies = [
[[package]]
name = "sqlite-wasm-rs"
version = "0.6.2"
version = "0.6.3"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "36bd8e29bf08189a005b2df1df99823aa0861cabe9044e5f31ed54ca292ee618"
checksum = "a6cd504cecbfe7eef649988840f9a6cb768d11085efec138f8e99f160632d867"
dependencies = [
"cc",
"rsqlite-vfs",
@@ -4427,9 +4394,9 @@ dependencies = [
[[package]]
name = "syn"
version = "3.0.9"
version = "3.0.10"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "d78c8dee4c7bf0e14673097256fed6142ce9d3b85a408189d07482442145823b"
checksum = "4ae9ccbea3a7b0b09443036490c8f34a8b1b760fd345e5c0dae0aac718faea79"
dependencies = [
"proc-macro2",
"quote",
@@ -4453,7 +4420,7 @@ checksum = "901704edd0dfe137f1987838ee4f259e4e063c31371bdb423f7ae38ec6f77f02"
dependencies = [
"proc-macro2",
"quote",
"syn 3.0.9",
"syn 3.0.10",
]
[[package]]
@@ -4503,8 +4470,8 @@ dependencies = [
"tao-macros",
"unicode-segmentation",
"url",
"windows 0.62.2",
"windows-core 0.62.2",
"windows",
"windows-core",
"windows-version",
"x11-dl",
]
@@ -4528,9 +4495,9 @@ checksum = "61c41af27dd6d1e27b1b16b489db798443478cef1f06a660c96db617ba5de3b1"
[[package]]
name = "tauri"
version = "2.12.5"
version = "2.12.6"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "5fb0244332cfb9cee7e2a568bf5da29a36ed8fdbd717f6f47a66b6b7b358c072"
checksum = "9c2a5cad3827d1fa46c206a6bcaee8ca14203e9b0aaabe447dd4acef33ecd065"
dependencies = [
"anyhow",
"bytes",
@@ -4574,14 +4541,14 @@ dependencies = [
"webkit2gtk",
"webview2-com",
"window-vibrancy",
"windows 0.62.2",
"windows",
]
[[package]]
name = "tauri-build"
version = "2.7.4"
version = "2.7.6"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "adddb0e648752aaac5da9c3c3c6a68e1e87cab55e3b757b18a9441ef8c3ac614"
checksum = "73d80784e874fa117b9b00a6680cf2f9b8a51bbd14406bea980cf8f328b00646"
dependencies = [
"anyhow",
"cargo_toml",
@@ -4602,9 +4569,9 @@ dependencies = [
[[package]]
name = "tauri-codegen"
version = "2.7.4"
version = "2.7.6"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "fb37631cf71dab5e8ab55e1bdd701e18a52653d90b78e71d0e5598b1e0a61316"
checksum = "c5dc6caab4da5646f57648f39b794bae118f0dd4a4305eeb8c892966171f4852"
dependencies = [
"base64 0.23.1",
"brotli",
@@ -4617,7 +4584,7 @@ dependencies = [
"semver",
"serde",
"serde_json",
"sha2 0.10.9",
"sha2 0.11.1",
"syn 2.0.119",
"tauri-utils",
"thiserror 2.0.21",
@@ -4629,9 +4596,9 @@ dependencies = [
[[package]]
name = "tauri-macros"
version = "2.7.4"
version = "2.7.6"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "0cc38db58854c10fb5f91a887ed8bf82d3239bb92b5d8db86eda09e96d9963d1"
checksum = "2831c5da8603a96b1efc0b650c2cb6decc69b6cda257d815fe70c7f5be53818e"
dependencies = [
"heck 0.5.0",
"proc-macro2",
@@ -4716,9 +4683,9 @@ dependencies = [
[[package]]
name = "tauri-plugin-opener"
version = "2.7.2"
version = "2.7.3"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "53810be1b4fed22bb6ac3f4cab5a2b80d9391d1af436bda145607532bc0bb219"
checksum = "54592c6718b42ab198bf11bda6a428a3553ca2f2f8e506df56f6a063ec328331"
dependencies = [
"dunce",
"glob",
@@ -4732,7 +4699,7 @@ dependencies = [
"tauri-plugin",
"thiserror 2.0.21",
"url",
"windows 0.62.2",
"windows",
"zbus",
]
@@ -4754,9 +4721,9 @@ dependencies = [
[[package]]
name = "tauri-runtime"
version = "2.12.2"
version = "2.12.4"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "7c55766d99cea69055904d1735b93c2049302b2e09effd462120deb5581d78e9"
checksum = "60c2b14bd5265b63993cdc34ad526fb836e0fd0cf64a4634a895db0784844d5e"
dependencies = [
"cookie",
"dpi",
@@ -4774,14 +4741,14 @@ dependencies = [
"url",
"webkit2gtk",
"webview2-com",
"windows 0.62.2",
"windows",
]
[[package]]
name = "tauri-runtime-wry"
version = "2.12.3"
version = "2.12.5"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "e1aa9d8b7a120f879f44fdc1053f7b7dbf416bf0bbc6a72b714dec46b782b52f"
checksum = "b8c14a025255cc9816d401635035075b09b6cc9973b7b8fd7b8fcb8753f30f92"
dependencies = [
"gtk",
"http",
@@ -4798,15 +4765,15 @@ dependencies = [
"url",
"webkit2gtk",
"webview2-com",
"windows 0.62.2",
"windows",
"wry",
]
[[package]]
name = "tauri-utils"
version = "2.10.2"
version = "2.10.4"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "362ab21cd4cc713f2a02b1a9b5688198b1541cfb6907c4281e9190e0f0ef4aa3"
checksum = "28d1d33d4453c5df0bf1672dbc7ada69d8ed74f56a4316d964a4aa73d4ecd3ad"
dependencies = [
"anyhow",
"brotli",
@@ -4916,7 +4883,7 @@ checksum = "fe5197923287db20a58125f0bc85c062f7f2c892de97b18c356f9efb14b28524"
dependencies = [
"proc-macro2",
"quote",
"syn 3.0.9",
"syn 3.0.10",
]
[[package]]
@@ -5012,7 +4979,7 @@ checksum = "78773a2a397f451582ce068015985c33193cf6dea8b74d2a639fe457b2f07b0e"
dependencies = [
"proc-macro2",
"quote",
"syn 3.0.9",
"syn 3.0.10",
]
[[package]]
@@ -5522,7 +5489,7 @@ dependencies = [
"bumpalo",
"proc-macro2",
"quote",
"syn 3.0.9",
"syn 3.0.10",
"wasm-bindgen-shared",
]
@@ -5711,8 +5678,8 @@ checksum = "3f89fca7a704cee10dcb3654c1dbb8941d1783132f1917358af75bec37a7d7e6"
dependencies = [
"webview2-com-macros",
"webview2-com-sys",
"windows 0.62.2",
"windows-core 0.62.2",
"windows",
"windows-core",
]
[[package]]
@@ -5733,8 +5700,8 @@ source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "b3a07132775117d6065853d9d1178157b8c90e228de47129d6bce2c7edebedfb"
dependencies = [
"thiserror 2.0.21",
"windows 0.62.2",
"windows-core 0.62.2",
"windows",
"windows-core",
]
[[package]]
@@ -5745,12 +5712,12 @@ checksum = "a28ac98ddc8b9274cb41bb4d9d4d5c425b6020c50c46f25559911905610b4a88"
[[package]]
name = "win32job"
version = "2.0.3"
version = "2.1.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "8c6a6724ccfbf34154a8691bd868b0fcd2be2ca3f7b47b32614654f1a01b191c"
checksum = "21b25acac91041257d64f5625690b626133e0ca9e4e17814552b5803b1a82f7c"
dependencies = [
"thiserror 1.0.69",
"windows 0.61.3",
"windows",
]
[[package]]
@@ -5800,38 +5767,16 @@ dependencies = [
"windows-version",
]
[[package]]
name = "windows"
version = "0.61.3"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "9babd3a767a4c1aef6900409f85f5d53ce2544ccdfaa86dad48c91782c6d6893"
dependencies = [
"windows-collections 0.2.0",
"windows-core 0.61.2",
"windows-future 0.2.1",
"windows-link 0.1.3",
"windows-numerics 0.2.0",
]
[[package]]
name = "windows"
version = "0.62.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "527fadee13e0c05939a6a05d5bd6eec6cd2e3dbd648b9f8e447c6518133d8580"
dependencies = [
"windows-collections 0.3.2",
"windows-core 0.62.2",
"windows-future 0.3.2",
"windows-numerics 0.3.1",
]
[[package]]
name = "windows-collections"
version = "0.2.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "3beeceb5e5cfd9eb1d76b381630e82c4241ccd0d27f1a39ed41b2760b255c5e8"
dependencies = [
"windows-core 0.61.2",
"windows-collections",
"windows-core",
"windows-future",
"windows-numerics",
]
[[package]]
@@ -5840,20 +5785,7 @@ version = "0.3.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "23b2d95af1a8a14a3c7367e1ed4fc9c20e0a26e79551b1454d72583c97cc6610"
dependencies = [
"windows-core 0.62.2",
]
[[package]]
name = "windows-core"
version = "0.61.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "c0fdd3ddb90610c7638aa2b3a3ab2904fb9e5cdbecc643ddb3647212781c4ae3"
dependencies = [
"windows-implement",
"windows-interface",
"windows-link 0.1.3",
"windows-result 0.3.4",
"windows-strings 0.4.2",
"windows-core",
]
[[package]]
@@ -5864,20 +5796,9 @@ checksum = "b8e83a14d34d0623b51dce9581199302a221863196a1dde71a7663a4c2be9deb"
dependencies = [
"windows-implement",
"windows-interface",
"windows-link 0.2.1",
"windows-result 0.4.1",
"windows-strings 0.5.1",
]
[[package]]
name = "windows-future"
version = "0.2.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "fc6a41e98427b19fe4b73c550f060b59fa592d7d686537eebf9385621bfbad8e"
dependencies = [
"windows-core 0.61.2",
"windows-link 0.1.3",
"windows-threading 0.1.0",
"windows-link",
"windows-result",
"windows-strings",
]
[[package]]
@@ -5886,9 +5807,9 @@ version = "0.3.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "e1d6f90251fe18a279739e78025bd6ddc52a7e22f921070ccdc67dde84c605cb"
dependencies = [
"windows-core 0.62.2",
"windows-link 0.2.1",
"windows-threading 0.2.1",
"windows-core",
"windows-link",
"windows-threading",
]
[[package]]
@@ -5913,45 +5834,20 @@ dependencies = [
"syn 2.0.119",
]
[[package]]
name = "windows-link"
version = "0.1.3"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "5e6ad25900d524eaabdbbb96d20b4311e1e7ae1699af4fb28c17ae66c80d798a"
[[package]]
name = "windows-link"
version = "0.2.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "f0805222e57f7521d6a62e36fa9163bc891acd422f971defe97d64e70d0a4fe5"
[[package]]
name = "windows-numerics"
version = "0.2.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "9150af68066c4c5c07ddc0ce30421554771e528bde427614c61038bc2c92c2b1"
dependencies = [
"windows-core 0.61.2",
"windows-link 0.1.3",
]
[[package]]
name = "windows-numerics"
version = "0.3.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "6e2e40844ac143cdb44aead537bbf727de9b044e107a0f1220392177d15b0f26"
dependencies = [
"windows-core 0.62.2",
"windows-link 0.2.1",
]
[[package]]
name = "windows-result"
version = "0.3.4"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "56f42bd332cc6c8eac5af113fc0c1fd6a8fd2aa08a0119358686e5160d0586c6"
dependencies = [
"windows-link 0.1.3",
"windows-core",
"windows-link",
]
[[package]]
@@ -5960,16 +5856,7 @@ version = "0.4.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "7781fa89eaf60850ac3d2da7af8e5242a5ea78d1a11c49bf2910bb5a73853eb5"
dependencies = [
"windows-link 0.2.1",
]
[[package]]
name = "windows-strings"
version = "0.4.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "56e6c93f3a0c3b36176cb1327a4958a0353d5d166c2a35cb268ace15e91d3b57"
dependencies = [
"windows-link 0.1.3",
"windows-link",
]
[[package]]
@@ -5978,7 +5865,7 @@ version = "0.5.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "7837d08f69c77cf6b07689544538e017c1bfcf57e34b4c0ff58e6c2cd3b37091"
dependencies = [
"windows-link 0.2.1",
"windows-link",
]
[[package]]
@@ -6005,7 +5892,7 @@ version = "0.61.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "ae137229bcbd6cdf0f7b80a31df61766145077ddf49416a728b02cb3921ff3fc"
dependencies = [
"windows-link 0.2.1",
"windows-link",
]
[[package]]
@@ -6039,22 +5926,13 @@ dependencies = [
"windows_x86_64_msvc 0.52.6",
]
[[package]]
name = "windows-threading"
version = "0.1.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "b66463ad2e0ea3bbf808b7f1d371311c80e115c0b71d60efc142cafbcfb057a6"
dependencies = [
"windows-link 0.1.3",
]
[[package]]
name = "windows-threading"
version = "0.2.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "3949bd5b99cafdf1c7ca86b43ca564028dfe27d66958f2470940f73d86d75b37"
dependencies = [
"windows-link 0.2.1",
"windows-link",
]
[[package]]
@@ -6063,7 +5941,7 @@ version = "0.1.7"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "e4060a1da109b9d0326b7262c8e12c84df67cc0dbc9e33cf49e01ccc2eb63631"
dependencies = [
"windows-link 0.2.1",
"windows-link",
]
[[package]]
@@ -6251,8 +6129,8 @@ dependencies = [
"webkit2gtk",
"webkit2gtk-sys",
"webview2-com",
"windows 0.62.2",
"windows-core 0.62.2",
"windows",
"windows-core",
"windows-version",
"x11-dl",
]
@@ -6321,7 +6199,7 @@ checksum = "ec8ebde2db3681e8c9980cc27822030e68752690ddfa9473e739aeb4dbde6d71"
dependencies = [
"proc-macro2",
"quote",
"syn 3.0.9",
"syn 3.0.10",
"synstructure",
]
@@ -6369,7 +6247,7 @@ dependencies = [
"proc-macro-crate 3.5.0",
"proc-macro2",
"quote",
"syn 3.0.9",
"syn 3.0.10",
"zbus_names",
"zvariant",
"zvariant_utils",
@@ -6432,7 +6310,7 @@ checksum = "f75b4683f6c7f45248d4d64056a24298c6281e0993356d7d1b4a1a962ef10d4a"
dependencies = [
"proc-macro2",
"quote",
"syn 3.0.9",
"syn 3.0.10",
"synstructure",
]
@@ -6472,7 +6350,7 @@ checksum = "c3743ddbf47738d929cd1ae2e199d40d0162979dfe31aef8ae646d2bf00bf97a"
dependencies = [
"proc-macro2",
"quote",
"syn 3.0.9",
"syn 3.0.10",
]
[[package]]
@@ -6526,7 +6404,7 @@ dependencies = [
"proc-macro-crate 3.5.0",
"proc-macro2",
"quote",
"syn 3.0.9",
"syn 3.0.10",
"zvariant_utils",
]
@@ -6539,6 +6417,6 @@ dependencies = [
"proc-macro2",
"quote",
"serde",
"syn 3.0.9",
"syn 3.0.10",
"winnow 1.0.4",
]
+1 -1
View File
@@ -7,7 +7,7 @@ version = "1.5.0"
edition = "2024"
rust-version = "1.99"
license = "GPL-3.0-only"
repository = "https://github.com/poli0981/pipdock"
repository = "https://github.com/poli0981org/pipdock"
authors = ["Kokone (poli0981)"]
# Applications, not libraries: nothing here belongs on crates.io, and cargo-deny treats a
# publishable crate's licence and path dependencies as a published one's (deny.toml).
+21 -15
View File
@@ -1,14 +1,14 @@
# PipDock
[![CI · Rust](https://github.com/poli0981/pipdock/actions/workflows/ci-rust.yml/badge.svg)](https://github.com/poli0981/pipdock/actions/workflows/ci-rust.yml)
[![CI · Node](https://github.com/poli0981/pipdock/actions/workflows/ci-node.yml/badge.svg)](https://github.com/poli0981/pipdock/actions/workflows/ci-node.yml)
[![CodeQL](https://github.com/poli0981/pipdock/actions/workflows/codeql.yml/badge.svg)](https://github.com/poli0981/pipdock/actions/workflows/codeql.yml)
[![Release](https://img.shields.io/github/v/release/poli0981/pipdock?display_name=tag&sort=semver)](https://github.com/poli0981/pipdock/releases)
[![CI · Rust](https://github.com/poli0981org/pipdock/actions/workflows/ci-rust.yml/badge.svg)](https://github.com/poli0981org/pipdock/actions/workflows/ci-rust.yml)
[![CI · Node](https://github.com/poli0981org/pipdock/actions/workflows/ci-node.yml/badge.svg)](https://github.com/poli0981org/pipdock/actions/workflows/ci-node.yml)
[![CodeQL](https://github.com/poli0981org/pipdock/actions/workflows/codeql.yml/badge.svg)](https://github.com/poli0981org/pipdock/actions/workflows/codeql.yml)
[![Release](https://img.shields.io/github/v/release/poli0981org/pipdock?display_name=tag&sort=semver)](https://github.com/poli0981org/pipdock/releases)
[![License: GPL-3.0](https://img.shields.io/badge/license-GPL--3.0-blue)](LICENSE)
**A friendly dock for your Python environments.** Inspect, install, update, and clean up Python packages in bulk — through a keyboard-first GUI or a scriptable CLI — without ever hand-typing another `pip install` incantation or guessing why an upgrade broke your project.
> Repo: `poli0981/pipdock` · License: **GPL-3.0-only** · Platform: **Windows 10/11** · Contact: [contact@poli0981.dev](mailto:contact@poli0981.dev) · [other channels](https://poli0981.dev/links/)
> Repo: `poli0981org/pipdock` · License: **GPL-3.0-only** · Platform: **Windows 10/11** · Contact: [contact@poli0981.dev](mailto:contact@poli0981.dev) · [other channels](https://poli0981.dev/links/)
---
@@ -73,7 +73,7 @@
## Install
Download the installer (NSIS `.exe` or `.msi`) from [GitHub Releases](https://github.com/poli0981/pipdock/releases).
Download the installer (NSIS `.exe` or `.msi`) from [GitHub Releases](https://github.com/poli0981org/pipdock/releases).
PipDock does not update itself — grab a new build from the same page when you want one. That is deliberate: a self-updater is a standing remote-code-execution path into a tool that already runs subprocesses against your interpreters, and it is not worth the convenience (see [docs/SECURITY.md](docs/SECURITY.md) §5).
@@ -88,10 +88,16 @@ PipDock does not update itself — grab a new build from the same page when you
> From 1.4.0 the `.exe` and `.msi` also carry a build-provenance attestation. A checksum published beside a file cannot prove where the file came from — whoever could replace one could replace both — but the attestation proves the installer was built by this repository's release workflow. With the [GitHub CLI](https://cli.github.com/):
>
> ```powershell
> gh attestation verify .\PipDock_<version>_x64-setup.exe --repo poli0981/pipdock
> gh attestation verify .\PipDock_<version>_x64-setup.exe --repo poli0981org/pipdock
> ```
>
> It succeeds only when GitHub holds an attestation from this repository for that exact file. If it fails, do not run the file.
> That is for 1.6.0 and later. **1.4.0 and 1.5.0 were built before the repository moved to the poli0981org organization** (2026-11-21), and their attestations stayed with the account that made them, so `--repo` finds none for them. Verify those against that account and the repository's old name instead:
>
> ```powershell
> gh attestation verify .\PipDock_1.5.0_x64-setup.exe --owner poli0981 --signer-repo poli0981/pipdock
> ```
>
> Either succeeds only when GitHub holds an attestation from this repository's release workflow for that exact file. If it fails, do not run the file.
## Quick start
@@ -115,10 +121,10 @@ pipdock snapshot rollback latest
## Documentation
**Using PipDock?** The [wiki](https://github.com/poli0981/pipdock/wiki) is the user-facing set —
[Getting Started](https://github.com/poli0981/pipdock/wiki/Getting-Started),
[Troubleshooting](https://github.com/poli0981/pipdock/wiki/Troubleshooting) and an
[FAQ](https://github.com/poli0981/pipdock/wiki/FAQ) that explains the design decisions rather than
**Using PipDock?** The [wiki](https://github.com/poli0981org/pipdock/wiki) is the user-facing set —
[Getting Started](https://github.com/poli0981org/pipdock/wiki/Getting-Started),
[Troubleshooting](https://github.com/poli0981org/pipdock/wiki/Troubleshooting) and an
[FAQ](https://github.com/poli0981org/pipdock/wiki/FAQ) that explains the design decisions rather than
just stating them. Everything below is for reading the code.
| Doc | Purpose |
@@ -134,7 +140,7 @@ just stating them. Everything below is for reading the code.
| [docs/ERROR-CATALOG.md](docs/ERROR-CATALOG.md) | Error codes, stderr detection patterns, user guidance |
| [docs/SECURITY.md](docs/SECURITY.md) | Threat model, PEP 668 policy, supply-chain hygiene |
| [docs/TESTING.md](docs/TESTING.md) | Test strategy incl. disposable-venv integration tests |
| [docs/RELEASE-CI.md](docs/RELEASE-CI.md) | CI callers into `poli0981/.github`, release pipeline |
| [docs/RELEASE-CI.md](docs/RELEASE-CI.md) | Workflows, branch protection, Dependabot, release pipeline |
| [docs/I18N.md](docs/I18N.md) | EN/VI localization rules |
| [docs/ROADMAP.md](docs/ROADMAP.md) | Spike week, milestones, exit criteria |
| [ACCESSIBILITY.md](ACCESSIBILITY.md) | What is supported, what has been tested, what is known not to work, and how to report a barrier |
@@ -146,7 +152,7 @@ just stating them. Everything below is for reading the code.
PipDock is built to work with a keyboard alone, with a screen reader and under a Windows contrast theme, and `pipdock` on the command line is plain text with no colour and nothing that animates. The target is WCAG 2.2 AA; it is a target and not a conformance claim, and [ACCESSIBILITY.md](ACCESSIBILITY.md) says exactly what has been tested, by whom, and what is known to fall short.
If something gets in your way, [open an accessibility issue](https://github.com/poli0981/pipdock/issues/new?template=accessibility.yml) or write to [accessibility@poli0981.dev](mailto:accessibility@poli0981.dev) — in English or Vietnamese, with no GitHub account needed and no diagnosis expected.
If something gets in your way, [open an accessibility issue](https://github.com/poli0981org/pipdock/issues/new?template=accessibility.yml) or write to [accessibility@poli0981.dev](mailto:accessibility@poli0981.dev) — in English or Vietnamese, with no GitHub account needed and no diagnosis expected.
## Contributing
@@ -172,4 +178,4 @@ PipDock is an independent project. It is not affiliated with or endorsed by the
PipDock là ứng dụng Windows (GUI + CLI) giúp kiểm tra, cài đặt, cập nhật và gỡ **hàng loạt** gói thư viện Python một cách an toàn: luôn chạy dry-run xem trước thay đổi, xử lý xung đột phiên bản với 3 lựa chọn rõ ràng, tự chụp snapshot trước mỗi lần chạy để rollback một chạm, cảnh báo khi gỡ gói mà gói khác đang phụ thuộc, và tổng kết "13 thành công, 2 thất bại" kèm lý do từng gói. Hỗ trợ engine pip hoặc uv (chọn trong Settings), tìm gói tức thì nhờ cache chỉ mục PyPI, kèm module Code Health (deptry/vulture/ruff) để dọn dependency thừa và dead code. Không thu thập dữ liệu. Giấy phép GPL-3.0.
**Khả năng tiếp cận:** PipDock dùng được chỉ với bàn phím, với trình đọc màn hình (đã thử với Narrator) và ở chế độ tương phản cao của Windows. Chi tiết, kể cả những gì chưa được kiểm thử, nằm trong [ACCESSIBILITY.md](ACCESSIBILITY.md). Nếu gặp rào cản, hãy [mở issue](https://github.com/poli0981/pipdock/issues/new?template=accessibility.yml) hoặc viết tới [accessibility@poli0981.dev](mailto:accessibility@poli0981.dev) — tiếng Việt cũng được.
**Khả năng tiếp cận:** PipDock dùng được chỉ với bàn phím, với trình đọc màn hình (đã thử với Narrator) và ở chế độ tương phản cao của Windows. Chi tiết, kể cả những gì chưa được kiểm thử, nằm trong [ACCESSIBILITY.md](ACCESSIBILITY.md). Nếu gặp rào cản, hãy [mở issue](https://github.com/poli0981org/pipdock/issues/new?template=accessibility.yml) hoặc viết tới [accessibility@poli0981.dev](mailto:accessibility@poli0981.dev) — tiếng Việt cũng được.
+1 -1
View File
@@ -21,7 +21,7 @@ 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.41.1", features = ["bundled"] }
rusqlite = { version = "0.42.0", features = ["bundled"] }
schemars = "1.2.3"
serde = { version = "1.0.229", features = ["derive"] }
serde_json = "1.0.154"
+1 -1
View File
@@ -17,7 +17,7 @@
use crate::model::EngineId;
/// Where the template lives. Not configurable: an issue URL a caller can set is a phishing vector.
const ISSUE_URL: &str = "https://github.com/poli0981/pipdock/issues/new?template=bug_report.yml";
const ISSUE_URL: &str = "https://github.com/poli0981org/pipdock/issues/new?template=bug_report.yml";
/// What a head knows about the failure it is reporting.
#[derive(Debug, Clone, Default)]
+1 -1
View File
@@ -116,5 +116,5 @@ thing to trust.
## Questions
`code@poli0981.dev`, or open a discussion at
[github.com/poli0981/pipdock](https://github.com/poli0981/pipdock/discussions). If you think
[github.com/poli0981org/pipdock](https://github.com/poli0981org/pipdock/discussions). If you think
something in this page is inaccurate, that is worth an issue.
+2 -2
View File
@@ -35,7 +35,7 @@ pipdock/
├─ src-tauri/ # Tauri 2 app (commands + events only)
├─ ui/ # React 19 + TS + Tailwind 4 + Vite 8 + Zustand + i18next
├─ legal/ # EULA, Disclaimer, Privacy, Third-Party (public — legal gate links here)
├─ .github/ # caller workflows into poli0981/.github + issue templates
├─ .github/ # workflows (all project-local), their scripts, issue templates
└─ docs/
```
@@ -269,7 +269,7 @@ Zustand stores: `useEnvStore`, `usePlanStore`, `useIndexStore`, `useSettingsStor
| rusqlite | 0.41.x (0.41.1; `libsqlite3-sys` 0.39.1, SQLite 3.54.1). 0.41 needed no code change: its new PRAGMA-name check accepts the three the store uses (`foreign_keys`, `journal_mode`, `user_version`), and its use-after-free fix is in `busy_handler`/`trace_v2`, which the store never registers. **Held at 0.37 until 1.4.0**: `libsqlite3-sys` 0.38's build script used the then-unstable `cfg_select!`, which did not compile on Rust 1.94.1. It is stable since 1.95, so the toolchain move met the hold's own condition. Nothing here used the `u64`/`usize` `ToSql` impls (off by default since 0.38) or `prepare_cached` (optional since 0.38). |
| rfd | 0.17.x (0.17.2), **the same rfd `tauri-plugin-dialog` compiles** — src-tauri takes it only for the start-up failure dialog, so its range follows the plugin's (^0.17 since 2.8.4) and `cargo tree -i rfd --target all` shows one copy. Held at 0.16 until 2026-11-04 for that reason. |
| TypeScript | **held at 6.0.x** (6.0.3; 7.0.2 is latest). `typescript-eslint` 8.72.1 still peers on `>=4.8.4 <6.1.0`, so anything from 6.1 on — 7.x included — fails `npm ci` with `ERESOLVE` before a single check runs. Revisit when typescript-eslint widens its range. |
| ESLint | **10.x (10.14.0), with `eslint-plugin-react` deliberately absent.** That plugin caps at ESLint 9, which drags in a `minimatch`/`brace-expansion` chain carrying six high-severity advisories and would fail `npm audit` in CI. The one rule it was wanted for — no hardcoded JSX strings (I18N §1) — is a local rule in `eslint.config.js`, which also implements the documented allowlist precisely. ESLint 10.14 and `typescript-eslint` 8.72 take `minimatch ^10.2`, and GHSA-g3hv-75wg-m249 (moderate, 2026-10-30) is fixed only in 11.0.1, so `npm audit` lists it; the gate is `--audit-level=high` and the patterns minimatch sees here are `eslint.config.js`'s own, so it is tolerated until ESLint moves rather than forced with an `overrides` across a major. |
| ESLint | **10.x (10.15.0), with `eslint-plugin-react` deliberately absent.** That plugin caps at ESLint 9, which drags in a `minimatch`/`brace-expansion` chain carrying six high-severity advisories and would fail `npm audit` in CI. The one rule it was wanted for — no hardcoded JSX strings (I18N §1) — is a local rule in `eslint.config.js`, which also implements the documented allowlist precisely. GHSA-g3hv-75wg-m249 (minimatch, moderate, 2026-10-30) was fixed only in 11.0.1, which ESLint 10.14 and `typescript-eslint` 8.72 did not accept, so it was tolerated rather than forced with an `overrides` across a major; ESLint 10.15 and `typescript-eslint` 8.73 moved to minimatch 11 (11.0.9 throughout, 2026-11-21), and `npm audit` is clean. |
**TypeScript is the one hold left, and Dependabot no longer proposes it:** `.github/dependabot.yml` ignores `typescript >=6.1.0`, with the reason beside the rule. A hold is a compile or install failure, not a preference, so such a PR would be closed rather than merged until the stated condition changes. `cargo audit` runs with `--deny warnings`, so a new informational advisory fails CI unless `.cargo/audit.toml` records why it is tolerated (SECURITY §7).
+1 -1
View File
@@ -522,7 +522,7 @@ lives in `pipdock-core` (`pins::suggest`, `requirements::parse`, `cache::usage`,
| Command palette | `Ctrl+K` | not applicable |
If you want one of these on the command line, say so in an
[issue](https://github.com/poli0981/pipdock/issues) — the core function is already there.
[issue](https://github.com/poli0981org/pipdock/issues) — the core function is already there.
**The PEP 668 override is GUI-only for a different reason, and stays so.** It is meant to be hard
to reach — a decision made in the GUI, behind a confirm — and a flag would put it one shell-history
+1 -1
View File
@@ -55,7 +55,7 @@ GUI: `code · localized one-liner · [Details ⌄ stderr tail ≤ 40 lines] · [
1. The GUI keeps a ring buffer (last 64 KB, `LOG_RING_BUFFER_BYTES`) of engine stdout/stderr, cleared when a plan begins. It holds engine output only: PipDock's own log (`data\logs\`, new in 1.4.0) is not in it and not in the URL — Settings' Logs row copies that log's tail on its own (`logs_tail`).
2. **Report bug** builds a prefilled GitHub new-issue URL against `.github/ISSUE_TEMPLATE/bug_report.yml`:
`https://github.com/poli0981/pipdock/issues/new?template=bug_report.yml&pd-version=…&os=…&engine=…&python=…&error-code=…&log-excerpt=…`
`https://github.com/poli0981org/pipdock/issues/new?template=bug_report.yml&pd-version=…&os=…&engine=…&python=…&error-code=…&log-excerpt=…`
Given the environment, `python` carries the engine's version too (`Python 3.12.4 · pip 26.2.1`); the GUI asks for it only when the user clicks, which costs a subprocess (U31).
3. URL budget: GitHub rejects very long URLs, so `log-excerpt` is cut, tail-biased, until its **percent-encoded** form fits 6 000 characters (`BUG_REPORT_EXCERPT_CHARS`). The cap was applied before encoding until 1.4.0, and encoding decides what GitHub sees — an accented letter costs up to nine bytes, a path separator three — so a log full of Vietnamese paths built a ~20 KB link and GitHub answered with an error page instead of the form (M51). The full log is not lost: the error row's *Copy full log* puts the whole ring on the clipboard (`BugReportLink.log`), and hides itself when there is nothing to copy.
4. Nothing is ever sent automatically — the user reviews the issue form in their browser. This is the entire "telemetry" story, and the row says so beside the button rather than leaving the user to guess what "Report bug" does.
+37 -44
View File
@@ -1,50 +1,42 @@
# PipDock — Release & CI
*Version 0.2 · 2026-07-27 · CI reuses the `poli0981/.github` ops repo where a suitable reusable workflow exists, and is project-local where one does not. The ops repo's suite was audited on 2026-07-27, and its CodeQL and notifier reusables re-read on 2026-10-17 (see §1 note) — do not assume a reusable exists without checking.*
*Version 0.3 · 2026-11-21 · Every workflow is project-local. Until the repository moved to the poli0981org organization (2026-11-21) four of them were callers into the owner's personal ops repo, `poli0981/.github`, at `@main`; §1 says what replaced each and why.*
## 1. Workflows (`.github/workflows/`)
| Workflow | Kind | Triggers | Jobs |
|---|---|---|---|
| `ci-rust.yml` | **project-local** | PR, push main | `fmt · clippy · test` (`windows-latest`): `cargo fmt --check`, clippy `-D warnings`, `cargo test --workspace --locked`. `cargo audit` (`ubuntu-latest`): a prebuilt `cargo-audit`, `--deny warnings`. `cargo deny` (`ubuntu-latest`): licences, sources, bans (`deny.toml`) |
| `ci-node.yml` | caller → ops `reusable-web-react.yml` + two local jobs | PR, push main | Node 26, `npm ci`, lint / typecheck / Vitest (each runs only if the npm script exists), `vite build`; local jobs `npm audit --audit-level=high` (after `npm ci --ignore-scripts`) and `tauri lockstep` (`scripts/check-tauri-lockstep.mjs`) |
| `ci-integration.yml` | project-local | PR touching what its end-to-end steps run through (the path list is in the file), nightly, Mondays, dispatch | Windows runner, Python 3.10 and 3.14: the disposable-venv suite (TESTING L2); Mondays and dispatch only, the fixture-drift re-capture against the newest pip and uv |
| `codeql.yml` | caller → ops `reusable-codeql.yml` | PR, push main, weekly | `languages: '["javascript-typescript", "rust", "actions"]'` |
| `security-scan.yml` | **project-local** | daily, dispatch | `cargo audit` and `npm audit` against `main` (SECURITY §7) |
| `sonar.yml` | **project-local** | PR, push main, dispatch (`main` only) | `token present` (`ubuntu-latest`) → `coverage · analysis` (`windows-latest`): vitest and `cargo llvm-cov` LCOV, clippy's JSON, then `sonarqube-scan-action` with `sonar.projectVersion` from `package.json` and `sonar.qualitygate.wait`. Skipped when the run has no `SONAR_TOKEN` (Dependabot and fork PRs), and for a dispatch from any branch but `main` — the plan analyses `main` and PRs only. `sonar-project.properties` holds the scope |
| `release.yml` | **project-local** | tag `v*`; dispatch (`tag`, `dry_run`) | `Build · checksum` (`windows-latest`, read-only) → `Attest · draft` (`ubuntu-latest`); see §3 |
| `announce-release.yml` | caller → ops `announce-release.yml` | release published; dispatch (re-runs) | Discord release announcement |
| `notify-ci-failure.yml` | caller → ops `notify-ci-failure.yml` | `workflow_run` completed for `CI / Rust`, `CI / Node`, `CI / Integration`, `Security scan`, `SonarCloud` — **by name** | Discord CI-failure notification |
| Workflow | Triggers | Jobs |
|---|---|---|
| `ci-rust.yml` | PR, push main | `fmt · clippy · test` (`windows-latest`): `cargo fmt --check`, clippy `-D warnings`, `cargo test --workspace --locked`. `cargo audit` (`ubuntu-latest`): a prebuilt `cargo-audit`, `--deny warnings`. `cargo deny` (`ubuntu-latest`): licences, sources, bans (`deny.toml`) |
| `ci-node.yml` | PR, push main | `lint · typecheck · test · build` (Node 26, `npm ci`, ESLint, `tsc`, Vitest, `vite build`); `npm audit --audit-level=high` (after `npm ci --ignore-scripts`); `npm licences` (`scripts/check-licenses.mjs` and its `node --test` suite — §2); `tauri lockstep` (`scripts/check-tauri-lockstep.mjs`) |
| `ci-integration.yml` | PR touching what its end-to-end steps run through (the path list is in the file), nightly, Mondays, dispatch | Windows runner, Python 3.10 and 3.14: the disposable-venv suite (TESTING L2); Mondays and dispatch only, the fixture-drift re-capture against the newest pip and uv |
| `codeql.yml` | PR, push main, weekly | `Analyze (<language>)` for `javascript-typescript`, `rust` and `actions`, all `build-mode: none` |
| `qodana.yml` | PR, push main, dispatch | `tokens present` → `qodana · rust` (Docker, `qodana-rust.yaml`) and `qodana · ts/js` (native, `qodana-js.yaml`), one Qodana Cloud project and token each; skipped without a token, like `sonar.yml` |
| `security-scan.yml` | daily, dispatch | `cargo audit` and `npm audit` against `main` (SECURITY §7) |
| `sonar.yml` | PR, push main, dispatch (`main` only) | `token present` (`ubuntu-latest`) → `coverage · analysis` (`windows-latest`): vitest and `cargo llvm-cov` LCOV, clippy's JSON, then `sonarqube-scan-action` with `sonar.projectVersion` from `package.json` and `sonar.qualitygate.wait`. Skipped when the run has no `SONAR_TOKEN` (Dependabot and fork PRs), and for a dispatch from any branch but `main` — the plan analyses `main` and PRs only. `sonar-project.properties` holds the scope and the project, `poli0981org_pipdock` since 2026-11-21 |
| `release.yml` | tag `v*`; dispatch (`tag`, `dry_run`) | `Build · checksum` (`windows-latest`, read-only) → `Attest · draft` (`ubuntu-latest`); see §3 |
| `notify.yml` | `workflow_run` of the workflows above, **by name**; release published; dispatch (`tag`, to announce again) | `ci-failure` → `DISCORD_CI_WEBHOOK`; `announce` → `DISCORD_RELEASES_WEBHOOK` and `DISCORD_REPO_WEBHOOK`, both through `.github/scripts/discord_notify.py` (standard library; `DRY_RUN=1` prints instead of posting) |
**`notify-ci-failure.yml` names its workflows, and a new workflow is added to it by its exact `name:`.** `workflows: ['*']` — the ops repo's own caller example — is not a wildcard to `workflow_run`: it matched nothing, so `main` stayed red from 2026-09-23 with every failure unreported. The reusable reports only failures on the default branch, and skips by name any workflow that has a dedicated notifier (CodeQL, Dependabot, deploy, Pages, release), which is why `CodeQL` and `Release` are not listed: listing them would only create skipped runs. A failed `Release` run therefore reaches no Discord channel; whoever pushed the tag has to watch it.
**`notify.yml` names its workflows, and a new workflow is added to it by its exact `name:`.** `workflows: ['*']` — the ops repo's old caller example — is not a wildcard to `workflow_run`: it matched nothing, so `main` stayed red from 2026-09-23 with every failure unreported. It reports a failure from any event but a pull request, filtering on the event alone — never on a branch name, which a fork controls. CodeQL, Qodana and Release are listed: the ops-repo notifier skipped anything named like CodeQL or Release because of "dedicated notifiers" PipDock never had, so a failed Release run reached no channel at all.
**Ops-repo audit (2026-07-27; CodeQL and the notifier re-read 2026-10-17) — why the table looks like this:**
**Why nothing calls the ops repo any more (2026-11-21).** The repository moved to the poli0981org organization so that the projects the owner maintains seriously sit apart from the ones made for fun, and a project in the organization should not run code another account can change. The four callers were exactly that: `@main` of `poli0981/.github`, unpinned, and its notifier checked out that repository's `main` and ran *its* Python script with PipDock's Discord webhooks in the environment. Each was small enough to copy, as OmniDeck — the organization's other project — had already done:
- The reusable suite covers assembly, c-cpp, chrome-extension, desktop-csharp, go, jvm, macos-swift, php, python, r, ruby and web-react. **There is no Rust reusable and no Tauri reusable**, and only `reusable-desktop-csharp.yml` uses a Windows runner — hence `ci-rust.yml`, `release.yml` and `security-scan.yml` are project-local. There is no SonarQube reusable either (re-checked 2026-10-25), so `sonar.yml` is project-local too.
- `reusable-web-react.yml` has **no `working-directory` input** (it runs `npm ci` at the repo root — hence `package.json` lives at the root with Vite's `root: './ui'`, see ARCHITECTURE §2) and **no `npm audit` step**, hence the extra local job.
- `reusable-codeql.yml` *documents* csharp, python, javascript-typescript, ruby, c-cpp, java-kotlin, go and swift, but hands `languages` straight to `codeql-action`, with `build-mode: none` for anything outside its autobuild list — so `rust` and `actions` run through it unchanged. This bullet said **CodeQL has no Rust analyzer**, so Rust's coverage came from clippy and `cargo audit` alone; the premise stopped being true in 2025, and `codeql.yml` now asks for both. Only the JavaScript/TypeScript analysis is a required check (§2).
- Portfolio notifications are **Discord-only**, driven by the ops repo's `.github/scripts/discord_notify.py`. There is no multi-platform `notify.py`.
- `reusable-web-react.yml` became `ci-node.yml`'s `lint · typecheck · test · build` job. It took two things with it: the `pages: write` and `id-token: write` grants its always-skipped Pages job forced on the caller (permissions are validated at startup regardless of `if:`), and the `dist` artifact nothing downloaded. Its missing `working-directory` input was why `package.json` sits at the repository root; the layout stays, because SonarCloud, Qodana, the scripts and Tauri's configuration all assume it now (ARCHITECTURE §2).
- `reusable-codeql.yml` became `codeql.yml`'s matrix job, with `codeql-action` pinned by commit where the reusable used `@v4`, and the same `category` values, so the alerts keep their history. Rust and Actions run as they did through the reusable, which handed `languages` straight to the action.
- `notify-ci-failure.yml` and `announce-release.yml` became `notify.yml`, with the script vendored from OmniDeck's self-contained notifier.
**Permissions matrix (explicit in every caller — the Phase-5 lesson: callers without a `permissions:` block default everything to `none`):**
**Every action is pinned by commit**, with its version in a comment for Dependabot to update — GitHub's own `actions/*` included, which had used major tags. A write permission sits on the job that needs it, never the workflow (SonarCloud S8233):
```yaml
# codeql.yml
# every workflow
permissions: { contents: read }
# codeql.yml — analyze
permissions: { actions: read, contents: read, packages: read, security-events: write }
# announce-release.yml / notify-ci-failure.yml
permissions: { contents: read, actions: read }
# ci-node.yml — the workflow, and the one job that calls the reusable
permissions: { contents: read }
# web: { contents: read, pages: write, id-token: write }
# release.yml — the workflow, then each job (§3)
permissions: { contents: read }
# build: { contents: read }
# publish: { contents: write, id-token: write, attestations: write }
# ci-rust.yml / ci-integration.yml / security-scan.yml / sonar.yml
permissions: { contents: read }
# qodana.yml — rust, js
permissions: { contents: read, checks: write, pull-requests: write, security-events: write }
# release.yml — publish (§3)
permissions: { contents: write, id-token: write, attestations: write }
```
**The lesson has a converse: a caller must grant at least what the callee's jobs declare, even for a job that will be skipped**, because permissions are validated at startup regardless of `if:`. `reusable-codeql.yml`'s analyze job asks for `packages: read`, and a caller without it got a `startup_failure` with no logs to explain it; `reusable-web-react.yml` declares a Pages-deploy job needing `pages: write` and `id-token: write`, skipped here by `deploy-pages: false` and validated all the same. A write is granted on the job that needs it, never the workflow (SonarCloud S8233), so no other job holds one. This block showed neither of those grants and gave `release.yml` `contents: write` across the board; since 1.4.0 the release's write lives on its publish job alone.
## 2. Branch & version policy
`main` protected (PR + green CI required). SemVer; tags `vX.Y.Z`, and `release.yml` refuses a tag that does not match all five version fields (§3). Commit subjects follow Conventional Commits, but nothing generates a changelog from them — this line said a generator did. `changelog/` is written by hand, for a user, under the rules in `changelog/README.md`; a draft release's notes are GitHub's generated list of merged pull requests.
@@ -53,7 +45,7 @@ permissions: { contents: read }
| Setting | Value | Why |
|---|---|---|
| Required checks | `fmt · clippy · test`, `cargo audit`, `lint · typecheck · test · build / build`, `npm audit`, `analyze / Analyze (javascript-typescript)` | the five that ran on **every** PR when the payload was set; four more do now (below) |
| Required checks | `fmt · clippy · test`, `cargo audit`, `cargo deny`, `lint · typecheck · test · build`, `npm audit`, `npm licences`, `tauri lockstep`, `Analyze (javascript-typescript)` | eight, all running on **every** PR (below) |
| Check app | pinned to `app_id: 15368` (`github-actions`) | a check from another app cannot satisfy a requirement |
| `enforce_admins` | `true` | the owner is the only contributor; protection that exempts them protects nothing |
| Required approvals | **0** | a solo owner cannot approve their own PR, so 1 would deadlock. A PR is still required |
@@ -64,17 +56,18 @@ permissions: { contents: read }
**`CI / Integration` is deliberately excluded, and this is the trap worth remembering:** its `pull_request` trigger is `paths:`-filtered, so on a docs-only or UI-only PR it never starts — and a required check that never starts stays *pending forever*. Requiring it would deadlock exactly the PRs it has no opinion about. `Re-capture against the latest engines` runs on no PR at all (Mondays and dispatch only) and is excluded for the same reason. The bare `CodeQL` check belongs to the `github-advanced-security` app rather than Actions and is left out too.
**Four more run on every PR and are not in the payload** — `cargo deny`, `tauri lockstep`, and CodeQL's `analyze / Analyze (rust)` and `analyze / Analyze (actions)` — all added in 1.4.0, after the five above were set (re-read 2026-10-17; the payload is unchanged). Until they are added, a red one is advice rather than a gate, which matters most for `tauri lockstep`: its whole purpose is to stop one half of a Tauri bump merging alone. `Security scan` runs on no PR and can never be required. SonarQube Cloud is not required either, in either form: `SonarCloud Code Analysis` is reported by the SonarCloud app, which the payload's `app_id` pin would not accept, and `sonar.yml`'s `coverage · analysis` is *skipped* on every PR without a token — Dependabot's — and a skipped job satisfies a requirement, so requiring it would gate exactly the PRs it never looks at.
**The payload has had two shapes.** The first, set on 2026-08-14, held five checks — `fmt · clippy · test`, `cargo audit`, `lint · typecheck · test · build / build`, `npm audit` and `analyze / Analyze (javascript-typescript)` — and two of those names were the ops repo's: a reusable workflow's check is `<caller job> / <callee job>`, so a rename upstream would have deadlocked every PipDock PR with no failing check to point at. The second, set on 2026-11-21 when the callers became local jobs, renames those two to `lint · typecheck · test · build` and `Analyze (javascript-typescript)` and adds three that had run on every PR since 1.4.0 as advice rather than gates: `cargo deny`, `npm licences` (new that day) and `tauri lockstep`, whose whole purpose is to stop one half of a Tauri bump merging alone. **A required name is now this repository's alone, so renaming a job means changing this payload in the same change.**
**Two required contexts are named by the ops repo, not by this one.** `analyze / Analyze (javascript-typescript)` and `lint · typecheck · test · build / build` come from `poli0981/.github`'s reusables. If either job is renamed upstream, every PipDock PR deadlocks with no obvious cause and no failing check to point at — the fix is to update the protection payload, not the code.
**Still not required, and why.** CodeQL's `Analyze (rust)` and `Analyze (actions)` run on every PR and stay advice. `Security scan` runs on no PR and can never be required. SonarQube Cloud is not required in either form: `SonarCloud Code Analysis` is reported by the SonarCloud app, which the payload's `app_id` pin would not accept, and `sonar.yml`'s `coverage · analysis` is *skipped* on every PR without a token — Dependabot's — and a skipped job satisfies a requirement, so requiring it would gate exactly the PRs it never looks at. Qodana is not required for the same reason, and because one of its two linters is a JetBrains early-access build behind an external service.
**If protection wedges**, `PUT` the same endpoint with `enforce_admins: false`, or `DELETE /branches/main/protection`. Worth knowing before it is needed rather than discovering it during an incident.
Dependency updates use **Dependabot** (`.github/dependabot.yml`) — the portfolio standard, as evidenced by the ops repo's `dependabot-summary.yml`; there is no Renovate configuration anywhere in the ops repo. **Five ecosystems**, weekly on Mondays: `cargo`, `npm`, `github-actions`, `pip` at `/tools` (the Code Health pins) and, since 1.4.0, `rust-toolchain` — the `rust-toolchain.toml` channel, in a PR of its own because a toolchain brings new clippy lints. Minor and patch updates are grouped per ecosystem; security advisories arrive as **immediate, ungrouped** PRs (Dependabot's default for security updates), and the `pip` ecosystem stays its own group so Code Health pin bumps are reviewable in isolation — a bump there also needs `tools/tools-constraints.txt` regenerated (the command is in its header), and `cargo test` fails until it is (CODE-HEALTH-SPEC §2). Watching `pip`/`uv` releases to trigger the parser-fixture job is the scheduled job in `ci-integration.yml`, not the dependency bot. Since 1.4.0:
Dependency updates use **Dependabot** (`.github/dependabot.yml`) — the standard of the owner's ops repo when the CI was set up, and of the poli0981org organization now; nothing here uses Renovate. **Five ecosystems**, weekly on Mondays: `cargo`, `npm`, `github-actions`, `pip` at `/tools` (the Code Health pins) and, since 1.4.0, `rust-toolchain` — the `rust-toolchain.toml` channel, in a PR of its own because a toolchain brings new clippy lints. Minor and patch updates are grouped per ecosystem; security advisories arrive as **immediate, ungrouped** PRs (Dependabot's default for security updates), and the `pip` ecosystem stays its own group so Code Health pin bumps are reviewable in isolation — a bump there also needs `tools/tools-constraints.txt` regenerated (the command is in its header), and `cargo test` fails until it is (CODE-HEALTH-SPEC §2). Watching `pip`/`uv` releases to trigger the parser-fixture job is the scheduled job in `ci-integration.yml`, not the dependency bot. Since 1.4.0:
- **Cooldowns.** A release must be 3 days old before cargo or npm proposes it (14 for a major), and 7 for Actions and the tool pins. Most yanked or compromised releases are pulled inside that window, and nothing here needs a dependency the day it ships.
- **Tauri moves in lockstep.** The `tauri` crate and `@tauri-apps/api` must share a minor or the app refuses to start, and Dependabot bumps Cargo and npm in separate PRs, each green on its own. So each ecosystem groups its Tauri packages (`tauri`, `tauri-*`; `@tauri-apps/*`) ahead of its catch-all group, and `ci-node.yml`'s `tauri lockstep` job fails either PR until its counterpart lands beside it, comparing the core and each plugin with its npm package on `Cargo.lock` and `package-lock.json` — what is built, not what the manifests ask for. **A multi-ecosystem group was considered and not used:** it would put both halves in one PR, but what it does to the dependencies outside its patterns is undocumented, and a wrong guess would silently stop every other update.
- **TypeScript is held below 6.1** (`ignore: typescript >=6.1.0`): typescript-eslint 8.71 peers `typescript >=4.8.4 <6.1.0`, so a 6.1 bump fails `npm ci` with ERESOLVE before a single check runs. Remove it once typescript-eslint widens its range (8.72 still peers `<6.1.0`, re-read 2026-10-25, with TypeScript at 7.0).
- **Tauri moves in lockstep.** The `tauri` crate and `@tauri-apps/api` must share a minor or the app refuses to start, and Dependabot bumps Cargo and npm in separate PRs, each green on its own. So each ecosystem groups its Tauri packages (`tauri`, `tauri-*`; `@tauri-apps/*`) apart from its catch-all group — by `exclude-patterns` on the catch-all, since 2026-11-21: Dependabot gives a dependency to the *most specific* matching group, it counts a group with `update-types` as more specific than one with patterns alone, and so the order this bullet used to rely on did nothing (that week's Tauri bumps landed in #116 and #118, the catch-alls) — and `ci-node.yml`'s `tauri lockstep` job fails either PR until its counterpart lands beside it, comparing the core and each plugin with its npm package on `Cargo.lock` and `package-lock.json` — what is built, not what the manifests ask for. **A multi-ecosystem group was considered and not used:** it would put both halves in one PR, but what it does to the dependencies outside its patterns is undocumented, and a wrong guess would silently stop every other update.
- **TypeScript is held below 6.1** (`ignore: typescript >=6.1.0`): typescript-eslint 8.71 peers `typescript >=4.8.4 <6.1.0`, so a 6.1 bump fails `npm ci` with ERESOLVE before a single check runs. Remove it once typescript-eslint widens its range (8.73 still peers `<6.1.0`, re-read 2026-11-21, with TypeScript at 7.0).
- **rfd is held below 0.18** (`ignore: rfd >=0.18.0`, cargo): src-tauri takes rfd only because tauri-plugin-dialog compiles it, and 2.8.4, the newest, still requires `^0.17` — so #112's rfd 0.18 alone would have put a second rfd in the binary. Remove it when the plugin moves, and bump both together.
- **Vitest moves as one** (group `vitest`: `vitest`, `@vitest/*`, every update type). `@vitest/coverage-v8`, which `sonar.yml` needs, peers `vitest` at its exact version, so a bump of either alone fails `npm ci` the way the TypeScript one would.
- **Labels.** PRs are labelled `dependencies` plus `rust`, `frontend`, `ci` or `code-health`, and the labels must exist in the repository or Dependabot opens its PRs without them (§5).
@@ -91,8 +84,8 @@ Two jobs, so the token that can write a release never runs the build (SECURITY
The frontend is built by tauri's `beforeBuildCommand`, so the workflow does not run `vite build` itself.
- **`SHA256SUMS.txt`**, LF line endings, written byte for byte: `Set-Content` wrote CRLF, and `sha256sum -c` on any other platform reads the CR as part of the file name and reports the file missing.
- The installers and the checksums are uploaded as the `release-artifacts` workflow artifact.
2. **`Attest · draft`** — Ubuntu runner, the only job granted `contents`, `id-token` and `attestations` write. It downloads the build, attests build provenance for the `.exe` and the `.msi` (`actions/attest-build-provenance`, verifiable with `gh attestation verify <file> --repo poli0981/pipdock`), and drafts the GitHub release with GitHub's generated notes and all three files (`softprops/action-gh-release`). Both actions are pinned by commit.
3. **Publishing the draft is a human decision**, taken per release; publishing fires `announce-release.yml`'s Discord announcement. For 1.4.0 the owner approved the plan and instructed the assistant to check the installers against `SHA256SUMS.txt` and then publish — `docs/AI-DISCLOSURE.md` records who did what.
2. **`Attest · draft`** — Ubuntu runner, the only job granted `contents`, `id-token` and `attestations` write. It downloads the build, attests build provenance for the `.exe` and the `.msi` (`actions/attest-build-provenance`, verifiable with `gh attestation verify <file> --repo poli0981org/pipdock`; an attestation stays with the account that made it, so 1.4.0 and 1.5.0, built before the move to the organization, verify with `--owner poli0981 --signer-repo poli0981/pipdock` and no longer with any `--repo`), and drafts the GitHub release with GitHub's generated notes and all three files (`softprops/action-gh-release`). Both actions are pinned by commit.
3. **Publishing the draft is a human decision**, taken per release; publishing fires `notify.yml`'s Discord announcement. For 1.4.0 the owner approved the plan and instructed the assistant to check the installers against `SHA256SUMS.txt` and then publish — `docs/AI-DISCLOSURE.md` records who did what.
**A dry run** — `workflow_dispatch` with `dry_run` — builds and checksums any ref, a branch before it merges included, and attests and drafts nothing, so the release recipe is tested before a tag depends on it. Without `dry_run`, dispatch builds a version tag only (the `tag` input re-runs one); a branch is refused.
@@ -100,7 +93,7 @@ This list had a fourth step — a post-release checklist issue, opened automatic
There is no signing step. **PipDock does not update itself** (SECURITY §5), so no `latest.json` is produced, no artifact is code-signed, and no keypair exists to manage. The attestation is signed through Sigstore with a short-lived certificate bound to the workflow run — which is why the publish job needs `id-token: write` — so it adds no key either.
Secrets bootstrap: set per-repo with `gh secret set` (the ops repo has no `setup-secrets.sh`) — the Discord webhooks the ops-repo notifiers expect (`DISCORD_RELEASES_WEBHOOK`, `DISCORD_REPO_WEBHOOK`, `DISCORD_CI_WEBHOOK`; the callers pass `secrets: inherit`). That is the whole list.
Secrets bootstrap: set per repository with `gh secret set`, none at the organization — the Discord webhooks `notify.yml` posts to (`DISCORD_RELEASES_WEBHOOK`, `DISCORD_REPO_WEBHOOK`, `DISCORD_CI_WEBHOOK`), `SONAR_TOKEN` for `sonar.yml` (re-issued for the `poli0981org` SonarQube Cloud organization on 2026-11-21), and `QODANA_TOKEN_RUST` and `QODANA_TOKEN_TS_JS` for the two Qodana Cloud projects `qodana.yml` reports to. That is the whole list; a transfer between owners keeps a repository's secrets, and it kept these.
## 4. Artifact & support policy
@@ -112,8 +105,8 @@ Two active lines at most: latest release gets features; previous minor gets secu
- [x] `.github/ISSUE_TEMPLATE/bug_report.yml` (shipped in this suite) + `config.yml` disabling blank issues.
- [x] `.github/dependabot.yml` covering cargo, npm, github-actions and the Code Health pins — and the Rust toolchain since 1.4.0.
- [x] `rust-toolchain.toml`, `.nvmrc` (26 — it said 24 until 1.5.0, a month after every workflow had moved to 26), `Cargo.lock`/`package-lock.json` committed.
- [x] **Repo settings (owner, via the GitHub UI or `gh` — not committable):** branch protection on `main`; disable Advanced Security → CodeQL *Default setup* (the reusable is advanced-setup and is rejected at upload time otherwise); enable Discussions for the issue-template contact links.
- [x] **Secrets via `gh secret set`:** the Discord webhooks (`DISCORD_RELEASES_WEBHOOK`, `DISCORD_REPO_WEBHOOK`, `DISCORD_CI_WEBHOOK`). No signing key — see §3.
- [x] **Repo settings (owner, via the GitHub UI or `gh` — not committable):** branch protection on `main`; disable Advanced Security → CodeQL *Default setup* (`codeql.yml` is an advanced setup, and is rejected at upload time otherwise); enable Discussions for the issue-template contact links.
- [x] **Secrets via `gh secret set`:** the Discord webhooks (`DISCORD_RELEASES_WEBHOOK`, `DISCORD_REPO_WEBHOOK`, `DISCORD_CI_WEBHOOK`), `SONAR_TOKEN`, `QODANA_TOKEN_RUST`, `QODANA_TOKEN_TS_JS` (§3). No signing key — see §3.
- [x] App icon settled (`src-tauri/icons/`). It was called a placeholder because nobody had chosen it; the owner chose it in Phase 4, which is what "a brand decision" needed.
- [x] README badges: CI, CodeQL, release, license.
- [x] **Labels (owner, repo settings — opened by 1.4.0):** `dependencies`, `rust`, `frontend`, `ci` and `code-health` for Dependabot (§2), and `triage` for `bug_report.yml`. None existed on 2026-10-17; all six did by 2026-11-10, when `accessibility` joined them for `accessibility.yml`.
+69
View File
@@ -1618,6 +1618,75 @@ said so in the PR: i18next 27 with react-i18next 18, and jsdom 31 — majors ins
window, the first with new defaults and stricter `t()` types that want a session of their own —
and rfd 0.18, which tauri-plugin-dialog 2.8.4 still pins below.
## After 1.5.0 — the move to poli0981org — **2026-11-21**
No version of its own; it ships inside 1.6.0. The owner moved the repository from `poli0981/pipdock`
to the **poli0981org** organization, to keep the projects maintained seriously apart from the ones
made for fun, and asked for everything that move touches: the alerts and the open Dependabot PRs,
Qodana on the owner's Ultimate plan, a licence check for the dependencies, CI that lives in the
repository ("mono repo"), and proof that the repository works in its new home. One PR,
[#119](https://github.com/poli0981org/pipdock/pull/119), superseding #113–#118.
**Where it started.** `main` had been red every day since 2026-11-18, and so had `cargo audit` on
all four of the week's Dependabot PRs: **RUSTSEC-2026-0543, chrono unmaintained** — in `Cargo.lock`,
and compiled into nothing.
| What | Now |
|---|---|
| chrono | Listed only because serde_with 3.24's `std` feature carries the weak features `chrono_0_4?/clock` and `chrono_0_4?/std`, which Cargo's lock resolution records even when nothing enables them; `cargo tree -i chrono --target all` prints nothing. Ignored in `.cargo/audit.toml` with that reason and its exit condition |
| Dependencies | #113–#118 cherry-picked (Rust 1.100.0, rusqlite 0.42.0, Tauri 2.12.6 with its npm half, the code-health pins, three actions, eleven npm packages) plus jsdom 31.0.1. No new clippy lint fired; neither rusqlite nor jsdom needed a code change; `tools-constraints.txt` regenerated by its header's command came out byte-identical to Dependabot's edit; the drift job, dispatched on the branch, found no engine output moved |
| minimatch | GHSA-g3hv-75wg-m249, tolerated since 2026-11-04, is gone: ESLint 10.15 and typescript-eslint 8.73 moved to minimatch 11 (11.0.9 throughout) |
| rfd 0.18 (#112) | Not taken. tauri-plugin-dialog 2.8.4 is still the newest and still requires `^0.17`; the ignore is back, with its exit condition |
| CI | Every workflow is local and every action pinned by commit (RELEASE-CI §1). Branch protection's payload changed with it: the two names the ops repo owned are renamed, and `cargo deny`, `npm licences` and `tauri lockstep` are required — eight checks |
| Licences | `npm licences`: 18 production packages, all MIT, Apache-2.0 or both. Proved to fail on a lockfile with one licence changed to CC-BY-4.0 |
| Qodana | Two Qodana Cloud projects, two configs, two tokens; full scans; a Rust baseline; `--fail-threshold 0` |
| SonarQube Cloud | `poli0981org_pipdock`, empty until this branch's first analysis; the old project keeps the history to 1.5.0 |
**What running found that reading did not:**
- **Dependabot's groups had never worked as written.** It gives a dependency to the *most specific*
group, and counts one with `update-types` as more specific than one with patterns alone — its own
log: "Skipping tauri-plugin-dialog for group 'tauri' - belongs to more specific group
'cargo-minor-patch'". The `tauri` groups caught nothing, while `dependabot.yml` said their order
kept Tauri out of the catch-alls. `exclude-patterns` on each catch-all now does.
- **Qodana's first Rust result was 0 problems, from 0 files analysed** — the same shape as 1.4.0's
"a check that cannot run must not report a pass". The linter container runs as the runner's
user, so rustup could not install the toolchain `rust-toolchain.toml` pins (it writes under
`/usr/local/rustup`, root's), `cargo metadata` failed, and RustRover loaded no Cargo project and
inspected nothing. Fixing that exposed the second half: `CARGO_HOME` was root's too, and the
registry download failed with "Permission denied". The bootstrap now points the job's own checkout
at the image's toolchain (1.94.0), and `CARGO_HOME` lives in the action's cache mount. The third
run analysed the workspace and found 62.
- **Of the 62, two are Critical and both are RustRover misreading code rustc compiles**: "value
used after being moved" on a `std::io::ErrorKind`, which is `Copy` (`exec.rs`, a test), and
"takes 2 parameters, 1 supplied" on an `async_trait` method called through `Box<dyn Engine>`
(`commands.rs`). The other 60 are Moderate style: 49 unnecessary path qualifications, 10
duplicated fragments, 1 trait-member order in a test fake. All 62 are the baseline; anything
new fails the run. Qodana for JS found six and all were fixed: five `React.*` types reached
through the UMD global rather than imported, and one High, `step` "possibly null" in
`PdPlanPanel` — which TypeScript narrows through an aliased condition and an optional chain, and
WebStorm's engine through neither, so it took an explicit `step !== null`.
- **SonarQube Cloud's first gate on the branch failed on code it had never seen**: `npm ci` running
lifecycle scripts in the web and Qodana jobs (githubactions:S6505). It ran the same way inside the
ops repo's reusable, where nothing analysed it. The one package with an install script is
fsevents, macOS-only; every `npm ci` in the workflows passes `--ignore-scripts` now.
- **An attestation stays with the account that made it.** After the transfer, README's own command
— `gh attestation verify <file> --repo poli0981/pipdock` — answered 404 for 1.5.0, and so does
`--repo poli0981org/pipdock`: the attestations of 1.4.0 and 1.5.0 are reachable only through the
user account that owned the repository when they were made. `--owner poli0981 --signer-repo
poli0981/pipdock` verifies them, checked against the real 1.5.0 installer. A user following
README to the letter would have been told not to run a genuine build.
- **A flaky runner, recorded so it is not chased again.** One integration job failed before any
test: rustup on the Windows image reported "detected conflict: `bin\cargo-clippy.exe`" while
installing Rust 1.100.0's components. The same toolchain installed cleanly on every other Windows
job, and the same job passed on the branch's next run.
**Kept as it was, on purpose**: `package.json` at the repository root — its original reason (the
reusable's missing `working-directory`) is gone, but SonarQube Cloud, Qodana, the scripts and
Tauri's configuration all assume the root now. And `pr-mode` is off in `qodana.yml`, where the plan
had put it back on: a whole scan is two to three minutes a part, so analysing only a pull
request's files would save little and make a result depend on which files changed.
## Standing risks
| Risk | Mitigation |
+7 -6
View File
@@ -57,7 +57,7 @@ That is a deliberate removal, not an omission. A self-updater is a permanent rem
What replaces it: SHA-256 checksums published per release (`SHA256SUMS.txt`) for manual verification, which the README tells users to check because SmartScreen warns on first run — the binaries are not EV-code-signed. Installer artifacts are NSIS + MSI from the Tauri bundler. Since 1.4.0 the checksum file has LF line endings, written byte for byte: the CRLF one `Set-Content` produced made `sha256sum -c` on any other platform read the CR as part of each file name and report every file missing.
**From 1.4.0, the installers carry a build-provenance attestation.** The release workflow attests the `.exe` and the `.msi` (`actions/attest-build-provenance`), and `gh attestation verify <file> --repo poli0981/pipdock` proves an installer was built by this repository's release workflow at the tagged commit — which a checksum published beside the file cannot, since whoever could replace one could replace both. The attestation is signed through Sigstore with a short-lived certificate bound to the workflow run, so it adds no key to keep.
**From 1.4.0, the installers carry a build-provenance attestation.** The release workflow attests the `.exe` and the `.msi` (`actions/attest-build-provenance`), and `gh attestation verify <file> --repo poli0981org/pipdock` proves an installer was built by this repository's release workflow at the tagged commit (for 1.4.0 and 1.5.0, built before the repository moved to the poli0981org organization on 2026-11-21, the attestations stayed with the account that made them: `--owner poli0981 --signer-repo poli0981/pipdock`) — which a checksum published beside the file cannot, since whoever could replace one could replace both. The attestation is signed through Sigstore with a short-lived certificate bound to the workflow run, so it adds no key to keep.
**The token that can write a release never runs the build.** Building executes third-party code — every crate's build script, every npm package's install script — so the build job holds a read-only token and keeps no credentials in its checkout; a separate job downloads what it produced, attests it and drafts the release, and is the only one granted `contents`, `id-token` and `attestations` write (RELEASE-CI §3).
@@ -76,15 +76,16 @@ pip-audit runs **from a venv of its own** in freeze-file mode: `Engine::freeze`
## 7. Supply chain of PipDock itself
- CI: `cargo audit` (RustSec) + `npm audit --audit-level=high` gate every PR, and since 1.4.0 run again **every day against `main`** (`security-scan.yml`). A PR gate fires only when something changes, so an advisory published against a dependency already merged waited for the next PR to trip over it — which is how `main` went red on 2026-09-23 with no PR open to say so — and, because the failure notifier matched no workflow at all, with nobody told. Dependabot keeps the Rust, npm, Actions and Code Health pins and the Rust toolchain current (see RELEASE-CI.md §2).
- The `cargo audit` gate is on **vulnerabilities** and is never relaxed. `.cargo/audit.toml` ignores a fixed list of *informational* advisories — unmaintained/unsound — on transitive crates PipDock cannot influence, chiefly Tauri's archived GTK3 bindings and, since 2026-10-20, zbus 5's `zvariant`/`zbus_names`/`zvariant_derive` (folded into zbus 6, which no Tauri plugin requires yet) — both stacks a Windows-only build never compiles. They are listed individually with justification so a **new** advisory still fails CI. Adding macOS/Linux builds (P2-1) is the point at which that block must be re-examined rather than extended.
- The `cargo audit` gate is on **vulnerabilities** and is never relaxed. `.cargo/audit.toml` ignores a fixed list of *informational* advisories — unmaintained/unsound — on transitive crates PipDock cannot influence, chiefly Tauri's archived GTK3 bindings and, since 2026-10-20, zbus 5's `zvariant`/`zbus_names`/`zvariant_derive` (folded into zbus 6, which no Tauri plugin requires yet) — both stacks a Windows-only build never compiles — and, since 2026-11-21, chrono, which `Cargo.lock` lists only because serde_with's weak `chrono_0_4?` features make Cargo record it, and which no target compiles at all. They are listed individually with justification so a **new** advisory still fails CI. Adding macOS/Linux builds (P2-1) is the point at which that block must be re-examined rather than extended.
- **That "still fails CI" has been true only since 1.4.0.** Informational advisories — unmaintained, unsound, yanked — are cargo-audit *warnings*, and `rustsec/audit-check@v2`, which ran the gate until then, let warnings through; on a pull request it failed only on *critical*, which is how September's advisories passed every PR. The gate is now a prebuilt `cargo-audit` (installed by `taiki-e/install-action`, pinned by commit) run with `--deny warnings`.
- `npm audit` installs with `npm ci --ignore-scripts`: it reads the lockfile and builds nothing, so no package's install script has a reason to run.
- **`cargo deny`** checks licences, sources and bans on every PR (`deny.toml`, since 1.4.0). Its licence allowlist — each entry GPL-3.0-compatible — turns THIRD-PARTY-NOTICES' "all bundled licenses are GPL-3.0-compatible" from a sentence into a test for every crate the Windows target resolves, transitive ones included; widening the list is a licensing decision, not a CI fix. Only crates.io may supply a crate — no git dependency, no other registry — and wildcard version requirements are refused. Advisories stay `cargo audit`'s, so there is one ignore list rather than two to keep in step. The npm half of the build has no equivalent licence check.
- **`cargo deny`** checks licences, sources and bans on every PR (`deny.toml`, since 1.4.0). Its licence allowlist — each entry GPL-3.0-compatible — turns THIRD-PARTY-NOTICES' "all bundled licenses are GPL-3.0-compatible" from a sentence into a test for every crate the Windows target resolves, transitive ones included; widening the list is a licensing decision, not a CI fix. Only crates.io may supply a crate — no git dependency, no other registry — and wildcard version requirements are refused. Advisories stay `cargo audit`'s, so there is one ignore list rather than two to keep in step. **The npm half has the same check since 2026-11-21**: `scripts/check-licenses.mjs` (`npm licences` in `ci-node.yml`) evaluates the SPDX expression of every package `package-lock.json` does not mark `dev` against the same allowlist, entry for entry, and fails on a package that declares none. Both are required checks (RELEASE-CI §2). Qodana's licence audit would have been a third, but it needs a plan the project does not have, and a check this small should not depend on one.
- `Cargo.lock` and `package-lock.json` committed; builds are `--locked`.
- **The environments PipDock builds for itself install a pinned tree.** Since 1.4.0 `tools/tools-constraints.txt` pins every package beneath the four tools, for the Code Health and the Security-tab venvs alike, so a broken or compromised release of `requests`, `rich` or `msgpack` no longer reaches every user on their next sync (CODE-HEALTH-SPEC §2). The pins are versions, not hashes; `--require-hashes` is in ROADMAP's Audit backlog.
- **Workflows** pin third-party actions by commit — `taiki-e/install-action`, `softprops/action-gh-release`, `SonarSource/sonarqube-scan-action`, and `actions/attest-build-provenance` too — while GitHub's own `actions/*` use major tags and the ops repo's reusables `@main`. A write permission sits on the job that needs it, not on the workflow (RELEASE-CI §1). A secret sits on the *step* that needs it: `sonar.yml` builds and tests — every crate's build script, every npm package's — before it scans, so `SONAR_TOKEN` is in the scanner step's environment alone, and the version spliced into the scanner's argv is checked against a version's shape first.
- **Workflows** pin every action by commit, with the version in a comment for Dependabot — GitHub's own `actions/*` and `github/codeql-action` included since 2026-11-21, when the last tags went. **No workflow calls another repository's.** Until the move to the poli0981org organization four were callers into the owner's personal ops repo at `@main`, and its notifier checked out that repository's `main` and ran its script with PipDock's Discord webhooks in the environment; those workflows are local now and the script is vendored (RELEASE-CI §1). A write permission sits on the job that needs it, not on the workflow (RELEASE-CI §1). A secret sits on the *step* that needs it: `sonar.yml` builds and tests — every crate's build script, every npm package's — before it scans, so `SONAR_TOKEN` is in the scanner step's environment alone, and the version spliced into the scanner's argv is checked against a version's shape first.
- **SonarQube Cloud** analyses every PR and `main` from CI (`sonar.yml`, since 2026-10-25) rather than by automatic analysis, which never saw the Rust code and could import no coverage. Its quality gate is not a required check (RELEASE-CI §2); a red gate on `main` fails the workflow and reaches Discord.
- CodeQL enabled via the ops-repo caller with the established permissions block, over **`javascript-typescript`, `rust` and `actions`**. This bullet said `javascript-typescript` only, because "CodeQL has no Rust analyzer" — which stopped being true in 2025, and the reusable hands any language straight to `codeql-action`. `actions` analyses the workflows themselves: write permissions at workflow level and unpinned third-party actions, the class of mistake SonarCloud had been finding by hand. Only the JavaScript/TypeScript analysis is a required check, so Rust's blocking static analysis is still clippy `-D warnings` plus `cargo audit` in `ci-rust.yml`.
- CodeQL runs from `codeql.yml` (a caller into the ops repo until 2026-11-21) over **`javascript-typescript`, `rust` and `actions`**. This bullet said `javascript-typescript` only, because "CodeQL has no Rust analyzer" — which stopped being true in 2025, and the ops repo's reusable handed any language straight to `codeql-action`. `actions` analyses the workflows themselves: write permissions at workflow level and unpinned third-party actions, the class of mistake SonarCloud had been finding by hand. Only the JavaScript/TypeScript analysis is a required check, so Rust's blocking static analysis is still clippy `-D warnings` plus `cargo audit` in `ci-rust.yml`.
- **Qodana** (`qodana.yml`, since 2026-11-21) runs JetBrains' inspections as two Qodana Cloud projects, one per half of the repository, each with its own token: RustRover's in a Linux container (`qodana-rust.yaml` — it cannot see `#[cfg(windows)]` code, which clippy, CodeQL and SonarQube Cloud cover on Windows) and WebStorm's natively (`qodana-js.yaml`). A run fails on a problem outside its committed baseline, and only those reach Code scanning. It is not a required check: one of its linters is an early-access build behind an external service, and Dependabot's PRs get no token.
- Third-party licenses tracked in `legal/THIRD-PARTY-NOTICES.md`, which names the **direct** dependencies the manifests declare and is reconciled against them by hand at each release. It is not generated: an earlier revision of both documents claimed `cargo about`/`license-checker` produced it into a `licenses/` directory, and no such config, directory or release step has ever existed. The complete resolved graph is `Cargo.lock` and `package-lock.json`, both committed. Generating the inventory is tracked as a Post-1.0 item; until it lands, the claim here matches what is done — and `cargo deny` checks the Rust licences without writing the inventory.
## 8. Data & privacy engineering
@@ -99,6 +100,6 @@ Logs contain package names and paths. There was no log until 1.4.0, while the Pr
## 9. Vulnerability reporting
Report privately through **GitHub Security Advisories** on `poli0981/pipdock`, or by email to `code@poli0981.dev`; target acknowledgment ≤ 7 days. Coordinated disclosure preferred; in-range CVEs in shipped dependencies trigger a patch release via the standard pipeline.
Report privately through **GitHub Security Advisories** on `poli0981org/pipdock`, or by email to `code@poli0981.dev`; target acknowledgment ≤ 7 days. Coordinated disclosure preferred; in-range CVEs in shipped dependencies trigger a patch release via the standard pipeline.
`.github/SECURITY.md` is the short pointer GitHub's *Security policy* tab renders, and it points here. This file is the policy; that one exists so the tab is not empty.
+1 -1
View File
@@ -45,7 +45,7 @@ Material changes to this policy bump the legal documents' version hash, and the
## 7. Contact
Privacy questions: email <contact@poli0981.dev>, or open a discussion or issue at <https://github.com/poli0981/pipdock>. The same contact details are listed in the application under **About**.
Privacy questions: email <contact@poli0981.dev>, or open a discussion or issue at <https://github.com/poli0981org/pipdock>. The same contact details are listed in the application under **About**.
---
+425 -488
View File
File diff suppressed because it is too large. Load diff
+14 -14
View File
@@ -7,12 +7,12 @@
"type": "module",
"repository": {
"type": "git",
"url": "git+https://github.com/poli0981/pipdock.git"
"url": "git+https://github.com/poli0981org/pipdock.git"
},
"bugs": {
"url": "https://github.com/poli0981/pipdock/issues"
"url": "https://github.com/poli0981org/pipdock/issues"
},
"homepage": "https://github.com/poli0981/pipdock#readme",
"homepage": "https://github.com/poli0981org/pipdock#readme",
"scripts": {
"dev": "vite",
"build": "vite build",
@@ -28,10 +28,10 @@
},
"dependencies": {
"@tanstack/react-virtual": "^3.14.26",
"@tauri-apps/api": "^2.12.4",
"@tauri-apps/api": "^2.12.5",
"@tauri-apps/plugin-clipboard-manager": "^2.5.0",
"@tauri-apps/plugin-dialog": "^2.8.4",
"@tauri-apps/plugin-opener": "^2.7.2",
"@tauri-apps/plugin-opener": "^2.7.3",
"i18next": "^26.7.2",
"react": "^19.3.1",
"react-dom": "^19.3.1",
@@ -41,23 +41,23 @@
"devDependencies": {
"@eslint/js": "^10.0.1",
"@tailwindcss/vite": "^4.3.5",
"@tauri-apps/cli": "^2.12.4",
"@tauri-apps/cli": "^2.12.5",
"@testing-library/jest-dom": "^7.0.1",
"@testing-library/react": "^16.3.3",
"@types/node": "^26.6.6",
"@types/react": "^19.3.0",
"@types/react-dom": "^19.3.0",
"@vitejs/plugin-react": "^6.2.1",
"@vitest/coverage-v8": "^5.1.0",
"axe-core": "^4.14.0",
"eslint": "^10.14.0",
"@vitejs/plugin-react": "^6.3.0",
"@vitest/coverage-v8": "^5.1.1",
"axe-core": "^4.14.1",
"eslint": "^10.15.0",
"eslint-plugin-react-hooks": "^7.1.1",
"eslint-plugin-react-refresh": "^0.5.7",
"jsdom": "^30.1.3",
"eslint-plugin-react-refresh": "^0.5.8",
"jsdom": "^31.0.1",
"tailwindcss": "^4.3.4",
"typescript": "^6.0.3",
"typescript-eslint": "^8.72.1",
"vite": "^8.3.6",
"typescript-eslint": "^8.73.0",
"vite": "^8.3.8",
"vitest": "^5.1.0"
}
}
+31
View File
@@ -0,0 +1,31 @@
# Qodana for the TypeScript/JavaScript half of the repository.
#
# The second of two Qodana Cloud projects (qodana-rust.yaml says why there are two), with its own
# token, QODANA_TOKEN_TS_JS. .github/workflows/qodana.yml passes `--linter qodana-js` and runs it
# natively on the runner, after `npm ci` with the Node version every other workflow uses, so the
# TypeScript service resolves the same node_modules the build does.
version: "1.0"
profile:
name: qodana.recommended
# The Rust workspace is qodana-rust.yaml's. generated.ts is `cargo run -p xtask -- bindings`
# output; fixing a finding in it by hand would be undone by the next regeneration.
exclude:
- name: All
paths:
- changelog
- coverage
- crates
- dist
- docs
- legal
- node_modules
- screenshot
- spikes
- src-tauri
- target
- tools
- ui/src/ipc/generated.ts
- xtask
+55
View File
@@ -0,0 +1,55 @@
# Qodana for the Rust half of the repository.
#
# One of two Qodana Cloud projects, each with its own token — QODANA_TOKEN_RUST for this file,
# QODANA_TOKEN_TS_JS for qodana-js.yaml — which is JetBrains' layout for a monorepo: every part is
# a project of its own, analysed by its own linter, and the two runs never report the same file.
# .github/workflows/qodana.yml runs both, and passes `--linter qodana-rust` there rather than here,
# so the linter's version is the action's and moves when Dependabot moves the action.
#
# **What this run cannot see.** The linter is RustRover in a Linux container (it has no native
# mode), so code behind `#[cfg(windows)]` — the PEP 514 registry, Job Objects, the `py` launcher —
# is inactive to it and is not analysed. Clippy, CodeQL and SonarQube Cloud run on Windows and
# cover it; this run adds RustRover's inspections over the code every platform compiles.
version: "1.0"
profile:
name: qodana.recommended
# **The container runs as the runner's user, not root**, so nothing can be installed into it — and
# that includes the toolchain rust-toolchain.toml pins: rustup writes under /usr/local/rustup,
# which root owns, so `cargo metadata` failed with "Permission denied", RustRover loaded no Cargo
# project, and the first run reported **0 problems after analysing nothing** (2026-11-21). The job's
# own checkout is writable, so the bootstrap points *that copy* at the toolchain the image ships;
# the repository's pin is untouched. (GTK and WebKitGTK cannot be installed either, so Tauri's
# Linux build scripts do not resolve; that touches macro expansion in src-tauri, not the analysis
# of the code around it.)
bootstrap: |
set -eu
shipped=$(rustup toolchain list | grep -m1 'default' | cut -d' ' -f1 || true)
if [ -z "$shipped" ]; then shipped=$(rustup toolchain list | head -n1 | cut -d' ' -f1); fi
printf '[toolchain]\nchannel = "%s"\n' "$shipped" > rust-toolchain.toml
echo "bootstrap: analysing with the image's $shipped instead of the pinned toolchain"
cargo metadata --format-version 1 --no-deps > /dev/null && echo "bootstrap: cargo metadata works"
# Everything that is not Rust belongs to qodana-js.yaml or to no linter at all. Fixtures are
# captured engine output and deliberately broken sample projects; snapshots are the CLI's goldens.
exclude:
- name: All
paths:
- .github
- changelog
- coverage
- crates/pipdock-cli/tests/snapshots
- crates/pipdock-core/tests/fixtures
- dist
- docs
- legal
- node_modules
- screenshot
- spikes
- src-tauri/gen
- src-tauri/icons
- target
- tools
- ui
+1 -1
View File
@@ -1,5 +1,5 @@
[toolchain]
channel = "1.99.1"
channel = "1.100.0"
components = ["rustfmt", "clippy"]
targets = ["x86_64-pc-windows-msvc"]
profile = "minimal"
+156
View File
@@ -0,0 +1,156 @@
/**
* Fail when a package the production build can bundle is not under a GPL-3.0-compatible licence.
*
* The npm half of what `deny.toml` does for the crates. THIRD-PARTY-NOTICES says every bundled
* licence is compatible with PipDock's GPL-3.0-only; `cargo deny` made that a test for the Rust
* side in 1.4.0, and until this script SECURITY §7 had to admit that "the npm half of the build
* has no equivalent licence check". Qodana's licence audit would have been one, but it needs the
* Ultimate Plus plan, and a check this small should not depend on a plan.
*
* It reads `package-lock.json` (lockfile v3) and installs nothing. "Production" is every package
* not marked `dev`: `devOptional` and `optional` ones stay in, because something the app depends
* on can pull them in. The allowlist mirrors `deny.toml`'s, entry for entry; widening either is a
* licensing decision, not a CI fix, and the two lists are meant to move together.
*/
import { readFileSync } from 'node:fs'
import { pathToFileURL } from 'node:url'
/** SPDX identifiers accepted on their own — exactly `deny.toml`'s `[licenses] allow`. */
export const ALLOWED = new Set([
'0BSD',
'Apache-2.0',
'BSD-3-Clause',
'BSL-1.0',
'CC0-1.0',
'ISC',
'MIT',
'MIT-0',
'MPL-2.0',
'Unicode-3.0',
'Unlicense',
'Zlib',
])
/**
* Packages whose lockfile entry carries no usable SPDX expression, each with the licence a person
* checked by hand and why. Empty: every production package declares one today.
*/
export const CHECKED_BY_HAND = new Map()
/** Split an SPDX expression into identifiers, operators and parentheses. */
export function tokenize(expression) {
return expression
.replace(/\(/g, ' ( ')
.replace(/\)/g, ' ) ')
.split(/\s+/)
.filter(Boolean)
}
/**
* Whether an SPDX expression can be satisfied with allowed licences: `OR` needs one side, `AND`
* both, `AND` binds tighter than `OR`, and parentheses group. A `WITH` exception is accepted only
* when the whole `id WITH exception` pair is allowed — none is today, so one fails and is looked
* at. Anything malformed throws, and the caller reports it as a violation.
*/
export function satisfiable(expression, allowed = ALLOWED) {
const tokens = tokenize(expression)
let at = 0
const peek = () => tokens[at]
const take = () => tokens[at++]
const primary = () => {
const token = take()
if (token === undefined) throw new Error(`unexpected end of "${expression}"`)
if (token === '(') {
const value = disjunction()
if (take() !== ')') throw new Error(`unbalanced parenthesis in "${expression}"`)
return value
}
if (token === ')' || token === 'AND' || token === 'OR' || token === 'WITH') {
throw new Error(`unexpected "${token}" in "${expression}"`)
}
if (peek() === 'WITH') {
take()
const exception = take()
if (exception === undefined) throw new Error(`"WITH" without an exception in "${expression}"`)
return allowed.has(`${token} WITH ${exception}`)
}
return allowed.has(token)
}
const conjunction = () => {
let value = primary()
while (peek() === 'AND') {
take()
value = primary() && value
}
return value
}
const disjunction = () => {
let value = conjunction()
while (peek() === 'OR') {
take()
value = conjunction() || value
}
return value
}
const result = disjunction()
if (at !== tokens.length) throw new Error(`trailing "${tokens[at]}" in "${expression}"`)
return result
}
/** `node_modules/a/node_modules/@scope/b` → `@scope/b`. */
export function packageName(path) {
return path.slice(path.lastIndexOf('node_modules/') + 'node_modules/'.length)
}
/** Every non-dev package in a lockfile-v3 `packages` map, as `{ name, version, license }`. */
export function productionPackages(lock) {
return Object.entries(lock.packages ?? {})
.filter(([path, entry]) => path !== '' && !entry.dev && !entry.link)
.map(([path, entry]) => ({ name: packageName(path), version: entry.version, license: entry.license }))
}
/** The packages that fail the allowlist, each with the reason. */
export function violations(packages, allowed = ALLOWED, checkedByHand = CHECKED_BY_HAND) {
const found = []
for (const pkg of packages) {
if (checkedByHand.has(pkg.name)) continue
if (typeof pkg.license !== 'string' || pkg.license.trim() === '') {
found.push({ ...pkg, reason: 'declares no SPDX licence expression' })
continue
}
try {
if (!satisfiable(pkg.license, allowed)) found.push({ ...pkg, reason: `${pkg.license} is not allowed` })
} catch (error) {
found.push({ ...pkg, reason: error.message })
}
}
return found
}
function main() {
const lock = JSON.parse(readFileSync('package-lock.json', 'utf8'))
if (lock.lockfileVersion !== 3) {
console.error(`package-lock.json is lockfile v${lock.lockfileVersion}; this check reads v3`)
return 1
}
const packages = productionPackages(lock)
const found = violations(packages)
for (const v of found) console.error(`${v.name}@${v.version}: ${v.reason}`)
if (found.length > 0) {
console.error(
`${found.length} of ${packages.length} production packages fail the licence allowlist. ` +
'Widening it is a licensing decision (deny.toml says why); CHECKED_BY_HAND is for a ' +
'package whose metadata is missing or wrong, with the licence a person verified.',
)
return 1
}
console.log(`${packages.length} production packages, every one under a GPL-3.0-compatible licence.`)
return 0
}
if (import.meta.url === pathToFileURL(process.argv[1] ?? '').href) {
process.exitCode = main()
}
+85
View File
@@ -0,0 +1,85 @@
// Run with `node --test scripts/*.test.mjs` — Node's built-in runner, so the check needs no
// dependency of its own (ci-node.yml's `npm licences` job).
import assert from 'node:assert/strict'
import { test } from 'node:test'
import { packageName, productionPackages, satisfiable, violations } from './check-licenses.mjs'
test('a single allowed identifier passes, an unknown one does not', () => {
assert.equal(satisfiable('MIT'), true)
assert.equal(satisfiable('CC-BY-4.0'), false)
assert.equal(satisfiable('GPL-2.0-only'), false)
})
test('OR needs one allowed side, AND needs both', () => {
assert.equal(satisfiable('MIT OR Apache-2.0'), true)
assert.equal(satisfiable('(GPL-2.0-only OR MIT)'), true)
assert.equal(satisfiable('MIT AND ISC'), true)
assert.equal(satisfiable('MIT AND CC-BY-4.0'), false)
})
test('AND binds tighter than OR, and parentheses override it', () => {
// MIT OR (CC-BY-4.0 AND ISC) — the MIT branch carries it.
assert.equal(satisfiable('MIT OR CC-BY-4.0 AND ISC'), true)
// (MIT OR CC-BY-4.0) AND WTFPL — WTFPL is not on the list, so nothing can satisfy it.
assert.equal(satisfiable('(MIT OR CC-BY-4.0) AND WTFPL'), false)
// An operand read left of OR must not be dropped when the right side is false.
assert.equal(satisfiable('Apache-2.0 OR CC-BY-4.0'), true)
})
test('an exception is accepted only as a whole pair someone allowed', () => {
assert.equal(satisfiable('Apache-2.0 WITH LLVM-exception'), false)
const allowed = new Set(['Apache-2.0 WITH LLVM-exception'])
assert.equal(satisfiable('Apache-2.0 WITH LLVM-exception', allowed), true)
})
test('a malformed expression throws rather than passing', () => {
assert.throws(() => satisfiable('(MIT'), /unbalanced|end/)
assert.throws(() => satisfiable('MIT OR'), /end/)
assert.throws(() => satisfiable('MIT ISC'), /trailing/)
assert.throws(() => satisfiable('AND MIT'), /unexpected/)
})
test('package names come from the last node_modules segment, scopes included', () => {
assert.equal(packageName('node_modules/react'), 'react')
assert.equal(packageName('node_modules/@tauri-apps/api'), '@tauri-apps/api')
assert.equal(packageName('node_modules/a/node_modules/@scope/b'), '@scope/b')
})
test('production means everything not marked dev, optional and devOptional included', () => {
const lock = {
packages: {
'': { name: 'pipdock', version: '1.0.0' },
'node_modules/react': { version: '19.0.0', license: 'MIT' },
'node_modules/vitest': { version: '5.0.0', license: 'MIT', dev: true },
'node_modules/fsevents': { version: '2.3.3', license: 'MIT', optional: true },
'node_modules/lightningcss': { version: '1.0.0', license: 'MPL-2.0', devOptional: true },
'node_modules/linked': { link: true, resolved: 'ui' },
},
}
assert.deepEqual(
productionPackages(lock).map((p) => p.name),
['react', 'fsevents', 'lightningcss'],
)
})
test('violations name the package and the reason, and a hand-checked one is skipped', () => {
const packages = [
{ name: 'ok', version: '1.0.0', license: 'MIT' },
{ name: 'data', version: '1.0.0', license: 'CC-BY-4.0' },
{ name: 'silent', version: '1.0.0', license: undefined },
{ name: 'broken', version: '1.0.0', license: '(MIT' },
]
const found = violations(packages)
assert.deepEqual(
found.map((v) => v.name),
['data', 'silent', 'broken'],
)
assert.match(found[1].reason, /no SPDX/)
const handChecked = new Map([['silent', 'MIT — LICENSE file read by hand']])
assert.deepEqual(
violations(packages, undefined, handChecked).map((v) => v.name),
['data', 'broken'],
)
})
+14 -4
View File
@@ -9,8 +9,11 @@
# first analysis with a new version is still measured against the old period, and the next one
# from the last analysis of the version before.
sonar.organization=poli0981
sonar.projectKey=poli0981_pipdock
# The project moved with the repository to the poli0981org organization on 2026-11-21. Its history
# up to 1.5.0 stays in the old project, `poli0981_pipdock` in the `poli0981` organization; this one
# started empty, so its first analysis of `main` is the baseline everything after it is new against.
sonar.organization=poli0981org
sonar.projectKey=poli0981org_pipdock
sonar.projectName=pipdock
sonar.sourceEncoding=UTF-8
@@ -25,7 +28,9 @@ sonar.test.inclusions=\
ui/src/**/*.test.ts,\
ui/src/**/*.test.tsx,\
ui/src/test/**,\
crates/*/tests/**
crates/*/tests/**,\
scripts/**/*.test.mjs,\
.github/scripts/**/*.test.*
# Images and fonts are tracked too, and the secrets sensor read every one as UTF-8 text and warned
# about each of them; nothing in them is code.
sonar.exclusions=\
@@ -33,6 +38,8 @@ sonar.exclusions=\
ui/src/**/*.test.tsx,\
ui/src/test/**,\
crates/*/tests/**,\
scripts/**/*.test.mjs,\
.github/scripts/**/*.test.*,\
**/*.png,\
**/*.ico,\
**/*.icns,\
@@ -57,10 +64,13 @@ sonar.javascript.lcov.reportPaths=coverage/lcov.info
# * probe.py runs inside the user's interpreter - the Rust suite parses canned output, and only
# ci-integration.yml runs it for real;
# * generated.ts is `cargo run -p xtask -- bindings` output, and the two entry points mount what
# the tests render directly.
# the tests render directly;
# * .github/ holds the workflows and the helpers they run on a runner (the Discord notifier since
# 2026-11-21) - they talk to GitHub's and Discord's APIs, which no test here reaches.
sonar.coverage.exclusions=\
xtask/**,\
scripts/**,\
.github/**,\
spikes/**,\
*.config.ts,\
*.config.js,\
+6 -6
View File
@@ -8,7 +8,7 @@ certifi==2026.10.23
# via requests
charset-normalizer==3.5.2
# via requests
click==8.5.0
click==8.5.1
# via deptry
colorama==0.4.6 ; sys_platform == 'win32'
# via deptry
@@ -20,13 +20,13 @@ deptry==0.25.1
# via -r tools/tools-requirements.txt
filelock==4.1.0 ; python_full_version < '3.11'
# via cachecontrol
filelock==4.2.7 ; python_full_version >= '3.11'
filelock==4.2.10 ; python_full_version >= '3.11'
# via cachecontrol
idna==3.20
# via requests
license-expression==30.4.4
# via cyclonedx-python-lib
markdown-it-py==4.2.0
markdown-it-py==4.3.0
# via rich
mdurl==0.1.2
# via markdown-it-py
@@ -48,9 +48,9 @@ pip-requirements-parser==32.0.1
# via pip-audit
platformdirs==4.12.4 ; python_full_version < '3.11'
# via pip-audit
platformdirs==4.14.3 ; python_full_version >= '3.11'
platformdirs==4.14.5 ; python_full_version >= '3.11'
# via pip-audit
py-serializable==2.1.0
py-serializable==2.2.0
# via cyclonedx-python-lib
pygments==2.21.0
# via rich
@@ -64,7 +64,7 @@ requirements-parser==0.13.1
# via deptry
rich==15.0.0
# via pip-audit
ruff==0.17.3
ruff==0.17.5
# via -r tools/tools-requirements.txt
sortedcontainers==2.4.0
# via cyclonedx-python-lib
+1 -1
View File
@@ -15,7 +15,7 @@
deptry==0.25.1
vulture==2.16
ruff==0.17.3
ruff==0.17.5
# The Security tab (PRD P1-1, shipped in 1.2.0). Installed into its own venv, not Code Health's
# (health::AUDIT_TOOLS), so a bump here never re-syncs the other one.
+2 -2
View File
@@ -1,4 +1,4 @@
import { useEffect, useRef, useState } from 'react'
import { useEffect, useRef, useState, type ReactNode } from 'react'
import { useTranslation } from 'react-i18next'
import { isBrowserShortcut } from '@/components/browserKeys'
@@ -34,7 +34,7 @@ import {
* hand-maintained negation of every key above it, so adding a screen meant editing two places and
* forgetting the second showed both at once. Tabs with no entry fall through to the placeholder.
*/
const SCREENS: Partial<Record<NavKey, React.ReactNode>> = {
const SCREENS: Partial<Record<NavKey, ReactNode>> = {
environments: <PdEnvironments />,
installed: <PdPackages mode="installed" />,
updates: <PdPackages mode="updates" />,
+3 -3
View File
@@ -26,7 +26,7 @@
* double-submitted and the user keeps reading what they were reading.
*/
import { useEffect, useId, useRef } from 'react'
import { useEffect, useId, useRef, type ReactNode } from 'react'
interface PdDialogProps {
/**
@@ -41,12 +41,12 @@ interface PdDialogProps {
/** Heading text, already localized. */
title: string
/** Body: the explanation, the list, whatever the caller needs. */
children: React.ReactNode
children: ReactNode
/** Cancel's label. Rendered first, focused on open. */
cancelLabel: string
onCancel: () => void
/** Everything other than Cancel, in the order UI-SPEC §5 lists them. */
actions: React.ReactNode
actions: ReactNode
/** While true every control is disabled: work is in flight and the answer would be stale. */
busy?: boolean
}
+3 -1
View File
@@ -6,6 +6,8 @@
* also why it passes the JSX-literal rule as a template expression rather than bare text.
*/
import type { ReactNode } from 'react'
interface PdEmptyStateProps {
/** Defaults to the terminal caret the rest of the app uses for a quiet statement of fact. */
glyph?: string
@@ -14,7 +16,7 @@ interface PdEmptyStateProps {
/** Optional second line, one shade quieter. */
hint?: string
/** Optional single action, per §7. */
action?: React.ReactNode
action?: ReactNode
}
export function PdEmptyState({ glyph = '▸', message, hint, action }: PdEmptyStateProps) {
+1 -1
View File
@@ -45,7 +45,7 @@ describe('Report bug', () => {
resetStore(useEnvStore)
useEnvStore.setState({ rows: [ROW], selected: ENV.interpreter })
vi.mocked(ipc.reportBugUrl).mockResolvedValue({
url: 'https://github.com/poli0981/pipdock/issues/new',
url: 'https://github.com/poli0981org/pipdock/issues/new',
log: '[log excerpt]',
})
})
+2 -2
View File
@@ -10,7 +10,7 @@
* test while a change to the dimming *rule* still does.
*/
import { memo } from 'react'
import { memo, type CSSProperties } from 'react'
import { useTranslation } from 'react-i18next'
import { PdBadge } from '@/components/PdBadge'
@@ -33,7 +33,7 @@ interface PdPackageRowProps {
/** Open the dependency view focused on this package — UI-SPEC §4's "details" (PRD P1-6). */
onDetails: (name: string) => void
/** The virtualizer's absolute positioning. */
style: React.CSSProperties
style: CSSProperties
}
function Row({
+1 -1
View File
@@ -11,7 +11,7 @@
*/
/** The repository itself. Inside `https://github.com/*`, which the opener capability allows. */
export const REPO = 'https://github.com/poli0981/pipdock'
export const REPO = 'https://github.com/poli0981org/pipdock'
const BLOB = `${REPO}/blob/main`
+1 -1
View File
@@ -448,7 +448,7 @@
},
"summary": "PipDock is provided without warranty. It runs pip or uv against environments you choose, and every change is previewed and snapshotted first — but you remain responsible for what you install.",
"accept": "I have read and accept these documents.",
"openFailed": "Could not open the link. The documents are on GitHub under poli0981/pipdock.",
"openFailed": "Could not open the link. The documents are on GitHub under poli0981org/pipdock.",
"close": "Close"
},
"about": {
+1 -1
View File
@@ -406,7 +406,7 @@
},
"summary": "PipDock được cung cấp không kèm bảo hành. Nó chạy pip hoặc uv trên những môi trường bạn chọn, và mọi thay đổi đều được xem trước và chụp ảnh trước — nhưng bạn vẫn chịu trách nhiệm về những gì mình cài.",
"accept": "Tôi đã đọc và chấp nhận các tài liệu này.",
"openFailed": "Không mở được liên kết. Các tài liệu nằm trên GitHub tại poli0981/pipdock.",
"openFailed": "Không mở được liên kết. Các tài liệu nằm trên GitHub tại poli0981org/pipdock.",
"close": "Đóng"
},
"about": {
+8 -3
View File
@@ -153,6 +153,11 @@ export function PdPlanPanel({ onFinished }: PdPlanPanelProps) {
forced.flatMap((f) => (f.blockers ?? []).map((b) => b.by ?? b.constraint)),
).size
const needsDecisions = step?.step === 'needsDecisions'
// Narrowed by an explicit null check, where it is read. TypeScript follows both an aliased
// condition (`needsDecisions`) and an optional chain back to `step`; Qodana's WebStorm engine
// follows neither, and reported `step.roundsRemaining` as a possible null twice (2026-11-21).
const roundsRemaining =
step !== null && step.step === 'needsDecisions' ? step.roundsRemaining : null
const exhausted = step?.step === 'roundsExhausted'
const nothingToDo = isRollback ? preview !== null && rollbackOps === 0 : step?.step === 'nothing'
const confirmable = isRollback ? preview !== null && rollbackOps > 0 : step !== null && step.step !== 'nothing'
@@ -193,11 +198,11 @@ export function PdPlanPanel({ onFinished }: PdPlanPanelProps) {
{/* The round counter UI-SPEC §4 now requires. `MAX_CONFLICT_ROUNDS` existed in core with
nothing surfacing it, so a user could hit the cap unwarned. */}
{needsDecisions ? (
{roundsRemaining === null ? null : (
<p className="mt-2 text-data text-text-dim">
{t('plan.roundsLeft', { count: step.roundsRemaining })}
{t('plan.roundsLeft', { count: roundsRemaining })}
</p>
) : null}
)}
{exhausted ? <p className="mt-2 text-data text-warn">{t('plan.roundsExhausted')}</p> : null}
{preview !== null ? (
+1 -1
View File
@@ -147,7 +147,7 @@ export function ipcMock(): IpcMock {
// with itself. A mock of the wrong *shape* is worse than no mock: it makes the seam it covers
// look tested.
reportBugUrl: vi.fn().mockResolvedValue({
url: 'https://github.com/poli0981/pipdock/issues/new',
url: 'https://github.com/poli0981org/pipdock/issues/new',
log: '[log excerpt]',
}),
// The one command in the surface that cannot fail — `app_info` is a `const fn` in Rust
+6 -5
View File
@@ -35,10 +35,11 @@ function devCsp(): Plugin {
}
}
// The frontend lives in ui/ per ARCHITECTURE §2, but package.json sits at the repo root so the
// ops-repo `reusable-web-react.yml` — which has no working-directory input — can run `npm ci` and
// `npm run build` unmodified. Hence root: './ui' with the bundle emitted to the repo-root dist/,
// which is that workflow's default dist-dir.
// The frontend lives in ui/ per ARCHITECTURE §2, but package.json sits at the repo root — first
// because the ops repo's reusable CI workflow had no working-directory input, and since CI went
// project-local (2026-11-21) because SonarCloud, Qodana, the scripts and Tauri's configuration all
// assume it. Hence root: './ui' with the bundle emitted to the repo-root dist/, which is where
// tauri.conf.json's frontendDist looks.
export default defineConfig({
root: './ui',
plugins: [react(), tailwindcss(), devCsp()],
@@ -68,7 +69,7 @@ export default defineConfig({
include: ['ui/src/**/*.test.{ts,tsx}'],
root: fileURLToPath(new URL('.', import.meta.url)),
// Off unless asked for (`npm run test:coverage`): sonar.yml imports the LCOV, and nothing
// else reads it, so the plain `npm test` the ops-repo reusable runs stays as fast as it was.
// else reads it, so the plain `npm test` ci-node.yml runs stays as fast as it was.
coverage: {
provider: 'v8',
// `lcovonly`: `lcov` adds an HTML report beside the file Sonar reads.