tyhpdef / phpunit-phpunit
Tyhp type definitions for phpunit/phpunit 12.5.35.
Package info
github.com/tyhpproject-packages/phpunit-phpunit
Type:metapackage
pkg:composer/tyhpdef/phpunit-phpunit
Requires
- tyhpdef/phpunit-phpunit-impl: ~12.5.35.0
Requires (Dev)
None
Suggests
None
Provides
None
Conflicts
None
Replaces
None
README
tyhpdef/phpunit-phpunit
Tyhp type definitions for phpunit/phpunit 12.5.35.
composer require --dev tyhpdef/phpunit-phpunit:12.5.35
This is a metapackage. Composer also installs tyhpdef/phpunit-phpunit-impl (type files).
Require this name, not tyhpdef/phpunit-phpunit-impl.
See https://tyhplang.com.
Maintain phpunit/phpunit? Ship the types yourself
If you are a Packagist maintainer of phpunit/phpunit, you can take over these
types.
Copy _tyhpdef/ from tyhpdef/phpunit-phpunit-impl (Apache-2.0; keep the NOTICE).
Then either:
- Bundle the files in
phpunit/phpunitand setextra.tyhp.packageon thatcomposer.json, plus"replace": { "tyhpdef/phpunit-phpunit": "self.version" }, or - Publish a sibling types package under your vendor, versioned with
phpunit/phpunit(sameX.Y.Z). Setextra.tyhp.packagethere,requirephpunit/phpunitwith a real constraint,"replace": { "tyhpdef/phpunit-phpunit": "self.version" }, and setextra.tyhp.tyhpdefonphpunit/phpunitto your sibling’s Composer name.
Ship that to Packagist first, then open an issue:
https://github.com/tyhpproject/tyhp-runtime-src/issues/new?template=tyhpdef-ownership.yml
We verify Packagist ownership and that the types parse and cover the PHP
API, then stop publishing community tags for those versions. We do not
transfer the tyhpdef/phpunit-phpunit Packagist name.
Full process: TYHPDEF_OWNERSHIP.md in
https://github.com/tyhpproject/tyhp-runtime-src