| commit 591166a63d287a4e6f262bed9aef61fd29bb3d05 parent eeb8e14abbc2c2e9b50b9b191d9db8e9bf2f9908 Author: sqzer <110329244+sqzer-x@users.noreply.github.com> Date: Fri, 25 Sep 2026 03:42:44 +0900 ci: pin actions to SHAs, scope permissions per job, refuse lockfile drift - checkout, withastro/action and deploy-pages are pinned to the commit SHAs of v7.0.1, v6.1.3 and v5.0.1. A moved tag can no longer change what runs without a change here. Dependabot proposes the bumps. - Workflow-level permissions are empty. The build job, which runs every npm dependency, mermaid and Chrome, gets contents: read. Only the deploy job holds pages: write and id-token: write, the minimum deploy-pages documents. - checkout no longer leaves the token in .git/config. - withastro/action installs with npm install, which quietly resolves new versions when package.json and the lockfile disagree. A dry-run npm ci before it fails the job instead, without installing or running any package script. Checked on npm 10 and 11. Diffstat:
|
blog~ Personal research notes. blog.sqzer.com |
| git clone https://github.com/debuman/blog.git |