Skip to content

v1.0.11

Choose a tag to compare

@somework somework released this 21 Sep 17:07
· 7 commits to main since this release
2b5dd2e

Adds format: html: the whole run as one self-contained page, made to be uploaded as an artifact. It carries the report, the release branches behind every finding, the advisories and the baseline comparison in a single file that opens from the downloaded artifact with no server and nothing fetched from anywhere, and the filters and the open package live in the URL, so a link points at what the sender was looking at — it is the format for the person who did not run it, a reviewer or whoever picks the ticket up a week later. The report file is named .html, so the artifact opens as a page rather than as text; all: true puts every checked package in it at roughly 4 KB each, and without it a 100-package lock lands around 250 KB. See the recipe.

Runs lockrot 0.10.0. A repository URL no longer carries its credentials into a report. A private Composer source is routinely configured with a token in the URL — https://gitlab-ci-token:$CI_JOB_TOKEN@… is how GitLab CI hands a job access to one, and Bitbucket app passwords take the same shape — and Composer keeps it in the lock because it has to fetch with it. lockrot 0.8.0 and 0.9.0 printed that value verbatim in --explain, so a workflow that passed --explain through args put a working token wherever the report went: the step log, the job summary, the uploaded file. Every repository URL lockrot prints now has its userinfo removed and its host kept, and a run that never asked for an explanation was not affected.

The JSON this action uploads also says what the run was told to do. --format=json now opens with a run block naming the project — from its own name in composer.json, or extra.lockrot.project where that is not the name to publish — along with the target PHP, the thresholds, the fail-on, the name of the lock and the verdicts the run counted as findings. Until now a report named the target PHP in one place only, inside an S5 signal, so a run where S5 never fired left no record of what it aimed at. Every finding also carries baseline: known, new or worsened, with the verdict the baseline accepted. Both are optional under the same schema number, so a step that reads the report keeps working — see the lockrot 0.10.0 release notes. See CHANGELOG.md.