npm (web/): - undici 7.30.1 through a "miniflare" override (GHSA-xjj6-f33q-929c, GHSA-4qv8-2p9j-2685, GHSA-f72v-6w45-q472). miniflare pins undici exactly and wrangler 4.152.0, the newest, still ships 7.29.1. Local tooling only. - zod 4.6.7 (GHSA-mrhx-c7xc-m3w5, via knip). - Minor/patch: @lucide/svelte 1.61.0, @tanstack/svelte-virtual 3.13.48, bits-ui 2.20.2, vite 8.3.5, wrangler 4.152.0, knip 6.43.0, @tauri-apps/cli 2.12.4. cargo (web/src-tauri/Cargo.lock, targeted updates only): - rustls 0.23.46 (RUSTSEC-2026-0346..0349), rustls-webpki 0.103.16 (RUSTSEC-2026-0382), webpki-root-certs 1.0.11 (RUSTSEC-2026-0383), tokio 1.54.1 (RUSTSEC-2026-0386), anyhow 1.0.104 (RUSTSEC-2026-0190), event-listener 5.4.2 (RUSTSEC-2026-0221), plist 1.10.3 -> quick-xml 0.42.0 (RUSTSEC-2026-0194/0195). Dependabot had none of these. - Left upstream: zip 4 (tauri-plugin-updater 2.14.0 asks for ^4), glib 0.18 (GTK 3), unmaintained proc-macro-error/zbus_names/zvariant. pip: certifi 2026.10.23, coverage 7.17.0 (tests), with every file's hash. CI: actions/checkout v4/v5 -> v6 and actions/setup-python v5 -> v6 everywhere (the Node 20 majors warned on every data job), rust-cache 2.9.3 by SHA. dependabot.yml says why those majors are taken by hand. CLAUDE.md: the undici override and when to drop it; why SvelteKit stays on 2 (GHSA-27mw-82g8-phjj and GHSA-pfhg-q3qv-9q6r need setHeaders or use:enhance, which the app does not have). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
68 lines
2.0 KiB
YAML
68 lines
2.0 KiB
YAML
name: Mark Dead Games
|
|
|
|
on:
|
|
schedule:
|
|
# Mon + Thu 04:30 UTC. Runs after Sun/Wed top-online refreshes player
|
|
# counts, so current_players is at most ~24h old when we read it.
|
|
- cron: '30 4 * * 1,4'
|
|
workflow_dispatch:
|
|
inputs:
|
|
dry_run:
|
|
description: 'Dry run (no write)'
|
|
type: boolean
|
|
default: false
|
|
days:
|
|
description: 'Threshold in days (default 14)'
|
|
default: '14'
|
|
|
|
permissions:
|
|
contents: write
|
|
actions: write
|
|
|
|
# queue: max - a run that finds another data job running waits its turn
|
|
# (first in, first out) instead of evicting the run already waiting.
|
|
concurrency:
|
|
group: data-write
|
|
cancel-in-progress: false
|
|
queue: max
|
|
|
|
jobs:
|
|
mark:
|
|
runs-on: ubuntu-latest
|
|
timeout-minutes: 20
|
|
steps:
|
|
- uses: actions/checkout@v6
|
|
# The tip of main when the job starts, not when it was queued: a run
|
|
# that waited behind a long data job would otherwise rewrite stale shards.
|
|
with:
|
|
ref: main
|
|
|
|
- uses: actions/setup-python@v6
|
|
with:
|
|
python-version: '3.15'
|
|
cache: 'pip'
|
|
cache-dependency-path: requirements.txt
|
|
|
|
- run: |
|
|
pip install --require-hashes --only-binary :all: -r requirements.txt
|
|
|
|
- name: Mark dead games
|
|
env:
|
|
DEAD_GAME_DAYS: ${{ inputs.days || '14' }}
|
|
run: |
|
|
if [ "${{ inputs.dry_run }}" = "true" ]; then
|
|
python scripts/mark_dead_games.py --dry-run
|
|
else
|
|
python scripts/mark_dead_games.py
|
|
fi
|
|
|
|
- name: Commit changes
|
|
if: ${{ inputs.dry_run != true }}
|
|
# Through commit_push.sh like every other data job: it rebases and
|
|
# retries when main moved during the run (a bare `git push` threw the
|
|
# run away), and it commits the whole tree, so scripts/removed_games.jsonl
|
|
# goes with the shards when save_main() applied a removal
|
|
# (scripts/core/blocklist.py).
|
|
run: |
|
|
bash ./bash/commit_push.sh "chore(data): mark dead games"
|