…ity-files

docs: centralize CODE_OF_CONDUCT and CONTRIBUTING at the monorepo root

…ity-files

docs: centralize CODE_OF_CONDUCT and CONTRIBUTING at the monorepo root

…ity-files

docs: centralize CODE_OF_CONDUCT and CONTRIBUTING at the monorepo root

…ity-files

docs: centralize CODE_OF_CONDUCT and CONTRIBUTING at the monorepo root

…ity-files

docs: centralize CODE_OF_CONDUCT and CONTRIBUTING at the monorepo root

…plex

feat: add Redis\Multiplexing adapter over Swoole TCP

…ity-files

docs: centralize CODE_OF_CONDUCT and CONTRIBUTING at the monorepo root

…ity-files

docs: centralize CODE_OF_CONDUCT and CONTRIBUTING at the monorepo root

feat: add get type method

…ity-files

docs: centralize CODE_OF_CONDUCT and CONTRIBUTING at the monorepo root

…ity-files

docs: centralize CODE_OF_CONDUCT and CONTRIBUTING at the monorepo root

…ity-files

docs: centralize CODE_OF_CONDUCT and CONTRIBUTING at the monorepo root

Cache 5.0.0 is released and this package pinned ^4, which blocks every consumer
downstream: appwrite cannot move to cache 5 while any dependency still requires
cache 4.

Nothing here needs to change to support it. Cache's major is for the
Redis\Multiplexing deadline behaviour and for requiring circuit-breaker ^0.4,
which dropped the threshold argument. This package uses neither — grep for
Multiplexing and CircuitBreaker across src/ and tests/ returns nothing, and the
generic Cache and Adapter surface is identical between 4 and 5.

Constrained as ^4.0 || ^5.0 rather than ^5.0 so this does not force the upgrade
on anyone still on cache 4.

Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>

Chore: Update Database

…ity-files

docs: centralize CODE_OF_CONDUCT and CONTRIBUTING at the monorepo root

Feat Redis Adapter

…ity-files

docs: centralize CODE_OF_CONDUCT and CONTRIBUTING at the monorepo root