[dependabot]

Bumps node-appwrite from 11.1.1 to 31.0.0.

Release notes

Sourced from node-appwrite's releases.

31.0.0

What's Changed

• Breaking: positional tablesDB, documentsDB and vectorsDB create and update take description before specification
• Breaking: positional functions.update takes description before emailEnabled
• Added: createQuery on databases, documentsDB and tablesDB to send list queries in the request body
• Added: account.listMemberships
• Added: optional description on create and update for databases, collections, tables, attributes, columns, indexes, buckets, functions, sites, variables, topics, webhooks and keys
• Added: description on the matching models
• Added: total on list methods in activities, backups, domains, mongo, mysql and postgresql
• Added: emails on messaging.createEmail and messaging.updateEmail
• Added: denyList on project.updatePasswordDictionaryPolicy, updatePasswordPersonalDataPolicy and their policy models
• Added: BillingPlan.functionsAllowCron
• Added: stripMetadata on storage.createBucket, updateBucket and the Bucket model
• Updated: package.json declares engines.node >=20.0.0

Full Changelog: appwrite/sdk-for-node@30.0.1...31.0.0

30.0.1

What's Changed

• Breaking: requests send X-Appwrite-Response-Format: 2.5.0; responses follow the 2.5 shapes
• Breaking: removed account.listLogs, users.listLogs and the Models.Log/Models.LogList models
• Breaking: removed organization.createKey, getKey, listKeys, updateKey and deleteKey, and OrganizationKeyScopes; use organization.listProjectKeys, getProjectKey, updateProjectKey and deleteProjectKey instead
• Breaking: removed Client.setDevKey, Models.DevKey and Project.devKeys
• Breaking: removed BillingPlanGroup.Starter; use BillingPlanGroup.Free
• Breaking: listSpecifications returns each specification's prices and overage rates on the row itself. Removed the list-level pricing field and the DedicatedDatabaseSpecificationPricing model
• Breaking: removed Block fields reason, projectName, region, organizationName, organizationId and billingPlan
• Breaking: OAuth2 resource params now take string[]
• Breaking: project.updateOAuth2Kakao takes enabled before prompt
• Breaking: BackupRestoration.options is now an object
• Breaking: nullable response fields are typed T | null; some became optional, such as BillingPlan.usage
• Added: Topic helper to build MQTT topics for push messages
• Added: mongo, mysql and postgresql promoteRestoration, restoreMode, targetName and autoPromote on createRestoration, and DedicatedDatabaseRestoration.restoreMode
• Added: proxy.createSMTPRule, the ProxyRuleProtocol enum and ProxyRule.protocol
• Added: emailEnabled on functions.update and Function, and ExecutionTrigger.Email
• Added: Query aggregates (count, countDistinct, sum, avg, min, max and more), groupBy, having, distinct, joins, relationship, covers, spatialEquals and page
• Added: Query.builder() to chain queries into a list
• Updated: nullable request params accept null, such as qos on topics and the Appwrite provider
• Updated: missing response fields fall back to their documented defaults
• Updated: OAuth2 prompt and native fields, PlatformAndroid.fingerprints and Identity.providerIdToken are always returned
• Fixed: list and object defaults filled into a response are copied per model, and object defaults are {} instead of []

30.0.0-rc.2

What's Changed

• Added: OAuth2 provider prompt enums (OAuth2Auth0Prompt, OAuth2GithubPrompt, and project variants)
• Added: Topic and ResolvedTopic exports
• Added: Models.Account and Models.OAuth2Webflow types
• Added: Webflow to the OAuthProvider and ProjectOAuthProviderId enums

... (truncated)

Changelog

Sourced from node-appwrite's changelog.

31.0.0

• Breaking: positional tablesDB, documentsDB and vectorsDB create and update take description before specification
• Breaking: positional functions.update takes description before emailEnabled
• Added: createQuery on databases, documentsDB and tablesDB to send list queries in the request body
• Added: account.listMemberships
• Added: optional description on create and update for databases, collections, tables, attributes, columns, indexes, buckets, functions, sites, variables, topics, webhooks and keys
• Added: description on the matching models
• Added: total on list methods in activities, backups, domains, mongo, mysql and postgresql
• Added: emails on messaging.createEmail and messaging.updateEmail
• Added: denyList on project.updatePasswordDictionaryPolicy, updatePasswordPersonalDataPolicy and their policy models
• Added: BillingPlan.functionsAllowCron
• Added: stripMetadata on storage.createBucket, updateBucket and the Bucket model
• Updated: package.json declares engines.node >=20.0.0

30.0.1

• Breaking: requests send X-Appwrite-Response-Format: 2.5.0; responses follow the 2.5 shapes
• Breaking: removed account.listLogs, users.listLogs and the Models.Log/Models.LogList models
• Breaking: removed organization.createKey, getKey, listKeys, updateKey and deleteKey, and OrganizationKeyScopes; use organization.listProjectKeys, getProjectKey, updateProjectKey and deleteProjectKey instead
• Breaking: removed Client.setDevKey, Models.DevKey and Project.devKeys
• Breaking: removed BillingPlanGroup.Starter; use BillingPlanGroup.Free
• Breaking: listSpecifications returns each specification's prices and overage rates on the row itself. Removed the list-level pricing field and the DedicatedDatabaseSpecificationPricing model
• Breaking: removed Block fields reason, projectName, region, organizationName, organizationId and billingPlan
• Breaking: OAuth2 resource params now take string[]
• Breaking: project.updateOAuth2Kakao takes enabled before prompt
• Breaking: BackupRestoration.options is now an object
• Breaking: nullable response fields are typed T | null; some became optional, such as BillingPlan.usage
• Added: Topic helper to build MQTT topics for push messages
• Added: mongo, mysql and postgresql promoteRestoration, restoreMode, targetName and autoPromote on createRestoration, and DedicatedDatabaseRestoration.restoreMode
• Added: proxy.createSMTPRule, the ProxyRuleProtocol enum and ProxyRule.protocol
• Added: emailEnabled on functions.update and Function, and ExecutionTrigger.Email
• Added: Query aggregates (count, countDistinct, sum, avg, min, max and more), groupBy, having, distinct, joins, relationship, covers, spatialEquals and page
• Added: Query.builder() to chain queries into a list
• Updated: nullable request params accept null, such as qos on topics and the Appwrite provider
• Updated: missing response fields fall back to their documented defaults
• Updated: OAuth2 prompt and native fields, PlatformAndroid.fingerprints and Identity.providerIdToken are always returned
• Fixed: list and object defaults filled into a response are copied per model, and object defaults are {} instead of []

29.4.0

• Added: domains service to manage domains, DNS records, email presets, prices, transfer status and zones
• Added: waf service with bypass, challenge, deny, rate-limit and redirect rules
• Added: account.createEmailVerificationOTP, updateEmailVerificationOTP, createRecoveryOTP and updateRecoveryOTP
• Added: account.createIdTokenSession and Identity.providerIdToken
• Added: oauth2.introspect
• Added: project environments with project.createEnvironment, getEnvironment, listEnvironments, updateEnvironment and deleteEnvironment
• Added: organization.createEphemeralProjectKey, listProjectKeys, getProjectKey, updateProjectKey and deleteProjectKey
• Added: Kakao, TikTok and Webflow OAuth2 providers with project.updateOAuth2Kakao, updateOAuth2TikTok and updateOAuth2Webflow
• Added: optional prompt on the Auth0, Discord, GitHub, Microsoft, Okta, Salesforce and Zoho OAuth2 settings, and native client IDs on Apple and Google

... (truncated)

Commits

• 3725f1c feat: SDK update for version 31.0.0 (#179)
• 13dbe4a Merge pull request #178 from appwrite/dev
• f646a57 docs: refresh README
• 3ffbdeb Merge commit 'a8e771af9014c509e9f802c7320451e7fa0936e6' into dev
• 320249d Merge pull request #177 from appwrite/dev
• a8e771a feat: SDK update for the 2.5.x majors
• 47f77d1 Merge remote-tracking branch 'origin/dev' into dev
• 6a35b33 feat: SDK update for the 2.5.x majors
• 698ec7e Merge remote-tracking branch 'origin/dev' into dev
• 013085c feat: SDK update for the 2.5.x majors
• Additional commits viewable in compare view

Maintainer changes

This version was pushed to npm by GitHub Actions, a new releaser for node-appwrite since your current version.

[hansi-codes]

🟡 Tier B · Needs changes before merging

The previously reported BigInt serialization issue remains open: syncing a document with a large integer can fail when Meilisearch JSON-serializes it.

The sync-with-Meilisearch template upgrades node-appwrite from the 11.x line to 31.0.0. The Bun lockfile is updated to match the new SDK and its dependency graph.

Verdict	New comments	Fixed	Still open
💬 Commented	0	0	1

Note

Not approving while a bug finding is open: Handle BigInt values before indexing documents

Fix with agent prompt

### Issue 1
bun/sync-with-meilisearch/package.json:12
**Handle BigInt values before indexing documents**

This SDK version returns integer fields above 2^53 as `BigInt`, but this function passes `documents` directly to `index.addDocuments`, whose JSON serialization throws on a `BigInt`. Syncs now fail when a collection contains such a value; the Node counterpart converts `BigInt` values to strings before indexing.

---

For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.

📂 Walkthrough · 2

File	Change
bun/sync-with-meilisearch/package.json	Bumps the node-appwrite dependency constraint to the 31.x major line.
bun/sync-with-meilisearch/bun.lock	Updates the locked node-appwrite package and its transitive dependencies.

⏳ Still open from earlier reviews · 1

• 🟡 Handle BigInt values before indexing documents · bun/sync-with-meilisearch/package.json:12

---

_{Reviewed e840a6b · Details · Comment @hansi-codes review to re-run, or mention @hansi-codes with a question.}

[hansi-codes]

🔵 Tier A · See the inline comments. Summary

[hansi-codes]

Handle BigInt values before indexing documents

This SDK version returns integer fields above 2^53 as BigInt, but this function passes documents directly to index.addDocuments, whose JSON serialization throws on a BigInt. Syncs now fail when a collection contains such a value; the Node counterpart converts BigInt values to strings before indexing.

Prompt To Fix With AI

This is a comment left during a code review.
Path: bun/sync-with-meilisearch/package.json
Line: 12

Comment:
**Handle BigInt values before indexing documents**

This SDK version returns integer fields above 2^53 as `BigInt`, but this function passes `documents` directly to `index.addDocuments`, whose JSON serialization throws on a `BigInt`. Syncs now fail when a collection contains such a value; the Node counterpart converts `BigInt` values to strings before indexing.

---

For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.

_{🟡 Minor · bug · Reply if this doesn't apply.}