tyhpdef / phpspec-prophecy

1.26.1 2026-10-05 18:49 UTC

Requires

• tyhpdef/phpspec-prophecy-impl: ~1.26.1.0

Apache-2.0

• static analysis
• dev

Published on Packagist.org on 2026-10-05 18:49 UTC

README

tyhpdef/phpspec-prophecy

Tyhp type definitions for phpspec/prophecy 1.26.1.

composer require --dev tyhpdef/phpspec-prophecy:1.26.1

This is a metapackage. Composer also installs tyhpdef/phpspec-prophecy-impl (type files). Require this name, not tyhpdef/phpspec-prophecy-impl.

See https://tyhplang.com.

Maintain phpspec/prophecy? Ship the types yourself

If you are a Packagist maintainer of phpspec/prophecy, you can take over these types.

Copy _tyhpdef/ from tyhpdef/phpspec-prophecy-impl (Apache-2.0; keep the NOTICE). Then either:

1. Bundle the files in phpspec/prophecy and set extra.tyhp.package on that composer.json, plus "replace": { "tyhpdef/phpspec-prophecy": "self.version" }, or
2. Publish a sibling types package under your vendor, versioned with phpspec/prophecy (same X.Y.Z). Set extra.tyhp.package there, require phpspec/prophecy with a real constraint, "replace": { "tyhpdef/phpspec-prophecy": "self.version" }, and set extra.tyhp.tyhpdef on phpspec/prophecy to 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/phpspec-prophecy Packagist name.

Full process: TYHPDEF_OWNERSHIP.md in https://github.com/tyhpproject/tyhp-runtime-src