tyhpdef / doctrine-annotations

2.0.2 2026-10-05 14:35 UTC

Requires

• tyhpdef/doctrine-annotations-impl: ~2.0.2.0

Apache-2.0

• static analysis
• dev

Published on Packagist.org on 2026-10-05 14:36 UTC

README

tyhpdef/doctrine-annotations

Tyhp type definitions for doctrine/annotations 2.0.2.

composer require --dev tyhpdef/doctrine-annotations:2.0.2

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

See https://tyhplang.com.

Maintain doctrine/annotations? Ship the types yourself

If you are a Packagist maintainer of doctrine/annotations, you can take over these types.

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

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

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