TrigenSoftware / simple-release / 33973859304

70%

push

github

docs: add the trusted publishing recipe to the docs and the skills (#198)

A new GitHub Action page describes publishing to npm without a token, as set up in nano_kit, Argue, and nanoviews: `id-token: write` on the publishing jobs, no `registry-url` and no `npm-token`, Node.js 24 for npm 11.5.1+, the trusted publisher registered per package and workflow file on npmjs.com (or with `npm trust github`), the snapshot job folded into `release.yml` behind a `snapshot` dispatch input because the registration is bound to the workflow file, automatic provenance, and the ENEEDAUTH causes. The release automation, snapshot, inputs, and agent skills pages link to it. The setup skill offers the token-or-trusted-publishing choice, detects it from existing workflows, generates the corresponding release job and the folded snapshot layout, and puts the registration into the final checklist; the simple-release-action skill recognizes the layout, dispatches snapshots through `release.yml`, and diagnoses ENEEDAUTH.

152 of 211 branches covered (72.04%)

Branch coverage included in aggregate %.

725 of 1046 relevant lines covered (69.31%)

11.05 hits per line