runward 0.44.0
The check talks to both forges: a GitLab CI template that runs the same check as the GitHub Action, a summary for the merge request, and the verdict as Code Quality and JUnit.
What changes
- On GitLab: a CI/CD template that runs the same check as the GitHub Action, attached to every release, for
include: remotewithintegrity:. report --format mdwrites a summary for the pull or merge request: the verdict, the gaps by kind, what is ratified and the assurance mode in force.check --codequalityandcheck --junitwrite the verdict as a Code Quality report and a JUnit XML, beside an unchanged output; a JUnit written by runward is refused as evidence.- A second package,
runward-forge, holds everything that talks to a forge:runwardkeeps no network code. - A row rewritten after it was ratified no longer counts as ratified, in any record.
- The GitLab template has run only in runward’s tests, and the bench is GitLab CE in CI: none of this has run on a real GitLab instance or in a customer’s chain.
Source
This note restates the section “0.44.0” of runward’s CHANGELOG, at the tag v0.44.0, and nothing else. The detail, and what it leaves out, is in the release notes on GitHub.