New checks - security.yml: dependency-review blocks PRs that add a high/critical advisory; actionlint + zizmor lint the workflows themselves (template injection, permissions, credential persistence, unpinned uses); OpenSSF Scorecard weekly and on main (published, not uploaded as alerts). - compliance.yml: REUSE lint over the whole repo (REUSE.toml + LICENSES/, no per-file headers) and Conventional-Commit PR titles. - rust.yml (src-tauri changes + weekly): rustfmt, clippy -D warnings, cargo test, and cargo-deny for RustSec advisories, licenses and sources. - ci.yml `check` gains: coverage thresholds (src/engine, worker), check:licenses, check:bundle, and a `wrangler deploy --dry-run`. Licensing - THIRD_PARTY_NOTICES.md is now generated from package.json, the installed packages and Cargo.toml/Cargo.lock (`npm run generate:third-party`); CI fails when it is stale or when anything bundled into the app carries a license outside the allowlist. It had drifted to React 18 / Vite 7 / Tailwind 3. - Vite's build.license emits the full text of every bundled package's license to /licenses/third-party.md (served publicly, before the gate). Bundle budget - scripts/check-bundle-size.ts measures what CLAUDE.md's "500KB" never defined: initial load (everything index.html references) <= 280 KB gzip (197 KB today) and no JS chunk over 500 KB raw. Coverage - @vitest/coverage-v8; thresholds sit just under today's numbers. The engine is at 89% lines / 64% functions — not the 100% CLAUDE.md claimed. Supply chain - Every third-party action pinned to a commit SHA (Dependabot updates the SHA and its version comment); checkout never persists credentials. - Release workflows: a `verify` job (typecheck, tests, version sync, Tauri alignment, tag == package version) gates the build; no dependency caches in release jobs; permissions granted per job. - Reusable Discord workflows receive only the secrets they declare instead of `secrets: inherit` (which exposed the Android signing keys to them). - Rust: cargo-deny found RUSTSEC-2026-0194/0195 (quick-xml DoS, via plist) that Dependabot had not raised; plist 1.10 brings quick-xml 0.41. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
52 lines
1.7 KiB
YAML
52 lines
1.7 KiB
YAML
name: Announce Release to Discord
|
|
|
|
on:
|
|
release:
|
|
types: [published]
|
|
workflow_dispatch:
|
|
inputs:
|
|
tag:
|
|
description: "Existing release tag to re-announce"
|
|
required: true
|
|
type: string
|
|
|
|
permissions:
|
|
contents: read
|
|
|
|
jobs:
|
|
link-discussion:
|
|
runs-on: ubuntu-latest
|
|
# `contents: write` edits the release; `discussions: write` lets GitHub
|
|
# auto-create the linked Discussion under the configured category.
|
|
permissions:
|
|
contents: write
|
|
discussions: write
|
|
steps:
|
|
- name: Link release to Announcements discussion
|
|
env:
|
|
GH_TOKEN: ${{ secrets.GITHUB_TOKEN }}
|
|
# Via env, never interpolated into the script: a tag name is
|
|
# user-controlled text.
|
|
TAG: ${{ github.event.release.tag_name || inputs.tag }}
|
|
REPO: ${{ github.repository }}
|
|
# Setting --discussion-category on a published release causes
|
|
# GitHub to auto-create the linked Discussion. Requires the
|
|
# repo to have Discussions enabled with an "Announcements"
|
|
# category (configured manually under repo Settings).
|
|
run: |
|
|
gh release edit "$TAG" --repo "$REPO" --discussion-category "Announcements"
|
|
|
|
announce:
|
|
needs: link-discussion
|
|
permissions:
|
|
contents: read
|
|
uses: poli0981/.github/.github/workflows/announce-release.yml@main
|
|
with:
|
|
tag_override: ${{ inputs.tag || '' }}
|
|
# Only what the shared workflow declares — not `inherit`, which would hand
|
|
# every repository secret (Android signing keys included) to it.
|
|
secrets:
|
|
DISCORD_RELEASES_WEBHOOK: ${{ secrets.DISCORD_RELEASES_WEBHOOK }}
|
|
DISCORD_REPO_WEBHOOK: ${{ secrets.DISCORD_REPO_WEBHOOK }}
|
|
DISCORD_PING_ROLE_ID: ${{ secrets.DISCORD_PING_ROLE_ID }}
|