[fabeat]

The instructions said:

composer validate is run without --strict on purpose: the manifest pins a commit of PHPPresentation's master branch rather than a tag, and --strict refuses that.

Both halves of that are false now. The manifest requires phpoffice/phppresentation at ~1.2.0 — a range of tags — and composer check runs composer validate --strict, which passes. The fixes this library needs are not in that release, so they come from a patch the library applies to the installed package, and the README says what a project has to allow for the patch to land.

The instructions now say that, and the command in the list carries --strict.

The claim is pinned

tests/Unit/dead-code.php guards the claims that have been wrong before, and it reads CONTRIBUTING.md along with the README and the changelog. Two entries are added:

'the manifest pins a commit of PHPPresentation master' => 'pins a commit of',
'the contributor instructions say validate runs without strict' => '`composer validate` is run **without**',

Both were shown to fire: with the old text restored, the guard fails with two problems; with the new text it passes.

It does not wait for the release. This is a documentation fix, not part of the release, so it stands on its own.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud