[renovate-appwrite]

This PR contains the following updates:

Package	Change	Age	Confidence
utopia-php/cache	4.* || 5.* → 4.* || 5.* || 7.*

---

Release Notes

utopia-php/cache

v7.0.0

Compare Source

Remove the legacy numeric-generation cache protocol (Cache::legacy(), the Legacy facade, Feature\Legacy and its adapter forwarding/Lua). This is a breaking API cleanup; the eviction-safe opaque CAS and writer coordination protocol remains unchanged.

Add Cache::withNamespace() as an independent view of the same backing cache. Purge recordings retain logical keys for replay. Cloud uses the existing v2: prefix to preserve warm data and cache identities while rolling from Bridge v2 to the replacement code; no cache flush or separate cache service is required. Keep old bridge images explicitly configured as v2 while they remain deployable rollback targets.

Published through the Appwrite monorepo release workflow from merged, checked commit 6f74288569b54991e922c36f7c8ac75360ef2970. Namespace, Redis/multiplexing eviction and released-bridge interoperability checks pass. See Appwrite #​15150 for validation and consumer dependencies.

Changes: appwrite/appwrite@cache/6.1.3...cache/7.0.0

v6.1.3

Compare Source

Preserve application list-cache behavior during the temporary rolling migration from cache 5.

• Legacy ordinary writes accept a physical TTL in the existing generation script, so expiring list-version markers do not refuse permission-changing writes.
• Legacy batch fills reuse the old envelope writer, keeping list reads warm without adding opaque fields to legacy hashes. Empty arrays and string zero fields remain cacheable.
• Conditional fills keep their generation and grace checks; opaque snapshots and CAS remain unavailable on the legacy facade.

Validation: 138 unit tests (4 existing skips), 128 transport tests /548 assertions, and package formatting, PHPStan and Rector checks. Redis and multiplexing regressions cover TTLs, warm batch fields, circuit-breaker forwarding and the released wire format.

For Appwrite's three-pass rolling bridge, use this release with database 9.1.1 or newer. Previous tags remain unchanged. This release does not deploy Appwrite Cloud.

v6.1.2

Compare Source

Complete the versioned-cache contracts used by the rolling migration bridge:

• Touching an in-memory entry invalidates its previous opaque lease, matching Redis.
• Conditional fills reject the same empty keys/data as ordinary saves.
• The legacy facade preserves the cache-5 0 hash sentinel for default-field writes and whole-key purges.
• Regression tests prove opaque snapshot/CAS calls cannot mutate legacy hashes.

Validation: 138 unit tests /313 assertions (four existing skips), 128 transport tests /534 assertions, Rector, Pint, PHPStan and the GitHub cache package gate pass. The cache-5 wire format and the 6.1.1 grace-window correction are preserved. Database 9.1.0 is compatible with this patch.

Review and changes · Changes since 6.1.1

For Appwrite rolling migrations, use cache 6.1.3 or newer: it preserves expiring list-version markers and legacy batch fills.

v6.1.1

Compare Source

Fix the temporary legacy migration facade when a nonzero fill-grace window is configured. Ordinary owner registrations now bypass the fill-only grace check, so rapid successive writes can proceed; conditional fills still respect the grace window.

This is required for the database 9.1 rolling bridge with Cloud's 1,000ms setting. Both Redis transports reproduce the regression on 6.1.0 and pass with the correction. The normal opaque v2 path is unchanged.

Validation: 136 unit tests /299 assertions (four existing skips), 128 transport tests /518 assertions, Rector, Pint, PHPStan, and the GitHub cache package gate pass. Real SQL successive-write coverage also passes in all three migration phases.

Source and review · Database bridge · Changes

v6.1.0

Compare Source

• fix(cache): reject opaque operations in the legacy facade
• fix(cache): preserve legacy hashes during bridge writes
• feat(cache): isolate temporary cache-5 migration facade

Changes: appwrite/appwrite@cache/6.0.0...cache/6.1.0

Migration note: use 6.1.1 for the rolling bridge. It corrects ordinary legacy registrations when a nonzero fill-grace window is configured; conditional fills remain fenced. The normal opaque v2 path is unchanged.

v6.0.0

Compare Source

Cache 6.0.0

Source: CI-green Appwrite commit d277e35; cache split 2fef3be.

Breaking changes: remove numeric generation leases and Feature\Leasable; use opaque versions, atomic snapshots and compare-and-swap. CAS returns the committed version or false on conflict; errors throw. Versioned operations respect circuit-breaker OPEN, failure counting and half-open recovery. Redis, multiplexed Redis and Memory support versioning; unsupported adapters refuse conditional fills.

If using Utopia Database, upgrade to database 9.x with cache 6.x. Drain all legacy writers, clear disposable cache data, deploy matching versions everywhere, then resume. Successful post-commit invalidation is still necessary.

Also includes the accumulated Redis lost-reply/timeout socket handling and filesystem flush fixes since 5.2.0, including dot-prefixed entries, preservation of the root directory, and propagation of deletion failures.

Full changes

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • Only on Monday (* * * * 1)
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR has been generated by Mend Renovate CLI.

[github-actions]

Thanks for contributing! This repository is a read-only mirror of packages/feed in Appwrite's private Cloud repository, so it cannot take pull requests: changes are made there and published here.