A housekeeping release so that a tag sits on a green CI run: the 0.6.0 commit shipped with a stale
generated case-studies page, which failed the PHP 8.4 job's staleness check while every test passed.
Deptrac now classifies third-party code too, and the README gained an architecture badge.
Fixed
docs/case-studies.mdregenerated for the two combined commands that changed in 0.6.0 (BookStack
socialite and Open Social); the CI check that compares the committed page with a fresh render had
been failing since the release commit.
Changed
-
Deptrac classifies third-party code as layers of its own (
Semver,ComposerPlugin,
ComposerApi,SymfonyConsole,SymfonyProcess,SymfonyYaml) and each project layer states
which it may use; the run fails on any dependency left unclassified (--fail-on-uncovered), so a
new library or a new corner of Composer's API has to be allowed deliberately. The report went from
296 uncovered dependencies to zero, with 468 allowed. The README carries an architecture badge fed
by the PHP 8.4 CI job ("passing", or "failing (n)"), next to the coverage badge. -
The roadmap page records the assurance work alongside the phases (adversarial review and rechecks,
the testing sprint, the Aikido answers, Deptrac) and marks Phase 5 as next.