Skip to content

feat: bump appwrite/appwrite to 24.*#113

Open
premtsd-code wants to merge 1 commit into
mainfrom
feat-bump-sdk-24
Open

feat: bump appwrite/appwrite to 24.*#113
premtsd-code wants to merge 1 commit into
mainfrom
feat-bump-sdk-24

Conversation

@premtsd-code
Copy link
Copy Markdown
Contributor

Bumps the appwrite/appwrite PHP SDK constraint from 23.* to 24.* so downstream consumers (e.g. utopia-php/migration) can pull in the 24.x SDK without dependency conflicts.

What's safe about this bump

The SDK 24.0.0 release introduced breaking changes — renamed Project-prefixed enums (AuthMethodProjectAuthMethodId, ServiceIdProjectServiceId, ProtocolIdProjectProtocolId, ProjectPolicyProjectPolicyId) — and 24.1.0 made BillingLimits inner fields nullable.

Abuse doesn't use any of the renamed symbols. Confirmed imports across src/:

use Appwrite\AppwriteException;
use Appwrite\Client;
use Appwrite\Enums\TablesDBIndexType;
use Appwrite\ID;
use Appwrite\Models\Row;
use Appwrite\Query;
use Appwrite\Services\TablesDB;

TablesDBIndexType was renamed back in 21.0.0 (IndexType split) and is stable in both 23.x and 24.x. All other symbols are unchanged.

Verification

  • composer update appwrite/appwrite -W resolves cleanly; lock updated to 24.1.0
  • php -l src/Abuse/Adapters/TimeLimit/Appwrite/TablesDB.php passes
  • composer check (phpstan level max) reports No errors on src/

Motivation

utopia-php/migration is bumping to 24.* on its add-policies-migration branch (PR #186) to pick up the BillingLimits nullable fix (which was crashing project-level migrations) and the new Project::get() / Project::getPolicy() methods. Right now, cloud's composer tree can't resolve migration@24.* alongside abuse@1.3.0 because of this constraint. Bumping here unblocks the chain.

The SDK's 24.0.0 release renamed several Project-prefixed enums
(AuthMethod -> ProjectAuthMethodId, ServiceId -> ProjectServiceId,
ProtocolId -> ProjectProtocolId, ProjectPolicy -> ProjectPolicyId) and
24.1.0 made BillingLimits fields nullable to match the server's sparse
'limits crossed' response.

abuse doesn't use any of the renamed enums; it only imports Client,
AppwriteException, ID, Query, Models\Row, Services\TablesDB, and
Enums\TablesDBIndexType -- all unchanged in 24.x.

Composer lock updated to 24.1.0. Bump unblocks downstream consumers
like utopia-php/migration that need the 24.x SDK.
@greptile-apps
Copy link
Copy Markdown

greptile-apps Bot commented May 20, 2026

Greptile Summary

This PR widens the appwrite/appwrite PHP SDK constraint from 23.* to 24.* and updates the lock file to 24.1.0, unblocking downstream consumers that require the 24.x line.

  • The only symbol from the SDK used in src/ is TablesDBIndexType (plus Client, ID, Query, Row, AppwriteException, and TablesDB service) — none of which were renamed or removed in the 24.x breaking-change window.
  • The lock resolves cleanly to 24.1.0; all other locked packages are untouched.

Confidence Score: 5/5

Safe to merge — only the SDK version constraint and lock file are touched, and the one file that consumes the SDK uses no symbols that changed in 24.x.

The change is a single-line constraint bump plus an updated lock file. The sole SDK consumer (TablesDB.php) imports only symbols that are stable across 23.x and 24.x, and the lock resolves cleanly to 24.1.0 without touching any other package.

No files require special attention.

Important Files Changed

Filename Overview
composer.json Bumps appwrite/appwrite constraint from 23.* to 24.*; no other changes.
composer.lock Lock file updated to resolve appwrite/appwrite at 24.1.0 (from 23.1.0); all other package entries unchanged.

Reviews (1): Last reviewed commit: "feat: bump appwrite/appwrite to 24.*" | Re-trigger Greptile

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant