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