31079741363
96%

Ran 06 Aug 2026 07:08AM UTC

Jobs 1

Files 8

Run time 1min

Badge

Embed ▾

Committed 06 Aug 2026 07:07AM UTC coverage: 94.079%. Remained the same

Build # 31079741363

Build Type

push

github

Committed by

web-flow

Commit Message

ci: check composer.lock in the validate gate (#50)

`composer validate` ran with --no-check-lock, on the reasoning recorded in the
comment beside it: composer.lock was untracked in some repos of the suite and
had drifted from composer.json in others, so blocking on lock state would have
blocked every PR. Lock state was reported by a separate advisory step instead.

Neither half of that is true any more. Every repo tracks its composer.lock, and
every lock is in sync with its composer.json. So the flag is dropped, the
duplicate advisory step goes, and the existing gate covers the lock directly —
one step doing the whole job rather than two doing half each.

Verified on the runner, not locally. The advisory step already ran exactly this
command there, so its recorded conclusion answers the question directly: success
in all 17 on the most recent main build. That distinction matters here — the
composer audit gate added just before this passed a local pre-flight on Composer
2.9 and then failed 9 of 17 in CI on 2.10, so a local green is not evidence
about the runner.

The advisory block keeps the Coveralls upload; asserted in the check below that
it is still there rather than removed along with the lock step.

Coverage Stats

143 of 152 relevant lines covered (94.08%)

3.09 hits per line

Jobs

ID	Job ID	Ran	Files	Coverage
1	31079741363.1	06 Aug 2026 07:08AM UTC	8	94.08	GitHub Action Run

bleedingdeacons / unity / 31079741363
96%

README BADGES
x

Markdown

Textile

RDoc

HTML

Rst

Jobs

Source Files on build 31079741363

bleedingdeacons / unity / 31079741363 96%

README BADGES x

Markdown

Textile

RDoc

HTML

Rst

Jobs

Source Files on build 31079741363

bleedingdeacons / unity / 31079741363
96%

README BADGES
x