Release

One version of the tool, cut by merging the version pull request (31 passages, no note) the pipeline (note: Pipeline) keeps open from the changesets (5 passages, no note): the merge (27 passages, no note) commit (29 passages, no note) is tagged v<major>.<minor>.<patch>, every published package (23 passages, no note) is packed and attached to a release with the standalone binaries (4 passages, no note) of the linter, the checksums (4 passages, no note) and the licence inventory (4 passages, no note), and the same tarballs (4 passages, no note) go to npm (7 passages, no note), the container image (5 passages, no note) to its registry (11 passages, no note) and the action (10 passages, no note) and the component (46 passages, no note) to their mirrors once the maintainer (note: Maintainer) has enabled (5 passages, no note) each publication (40 passages, no note). Every form (52 passages, no note) of a version names the same commit, so a version pinned (19 passages, no note) in a pipeline, a hook (4 passages, no note) or an image (18 passages, no note) is one registry of checks with one behaviour, and the version of the tool written in the site (note: Site) and the model (note: Model) is that of the release.