feat: SDK update for version 15.6.0 - #107
Conversation
Greptile SummaryThis PR updates the Console SDK to version 15.6.0.
Confidence Score: 4/5The PR appears safe to merge, with a non-blocking Node 18 compatibility inconsistency in the new dependency override. The SDK methods and model updates follow established generated-code conventions, but the overridden development dependency excludes a Node.js version that the package still claims to support. Files Needing Attention: package.json, package-lock.json Important Files Changed
Prompt To Fix All With AI### Issue 1
package.json:46-48
**Override conflicts with Node 18**
The package declares support for Node.js 18, but the new override forces `brace-expansion@5.0.8`, which declares Node `20 || >=22`; Node 18 installations therefore report an unsupported engine and fail when strict engine enforcement is enabled, blocking development dependency installation and SDK builds.
---
For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.Reviews (1): Last reviewed commit: "chore: update Console SDK to 15.6.0" | Re-trigger Greptile |
| "typescript": "5.9.3" | ||
| }, | ||
| "overrides": { |
There was a problem hiding this comment.
Override conflicts with Node 18
The package declares support for Node.js 18, but the new override forces brace-expansion@5.0.8, which declares Node 20 || >=22; Node 18 installations therefore report an unsupported engine and fail when strict engine enforcement is enabled, blocking development dependency installation and SDK builds.
Prompt To Fix With AI
This is a comment left during a code review.
Path: package.json
Line: 46-48
Comment:
**Override conflicts with Node 18**
The package declares support for Node.js 18, but the new override forces `brace-expansion@5.0.8`, which declares Node `20 || >=22`; Node 18 installations therefore report an unsupported engine and fail when strict engine enforcement is enabled, blocking development dependency installation and SDK builds.
---
For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.
This PR contains updates to the SDK for version 15.6.0.
What's Changed
appsinstallation methodslistInstallations,getInstallation,deleteInstallation, andcreateInstallationTokenvcs.listNamespaces()for listing provider namespaces available to an installationproviderNamespaceparameter tovcs.createRepository()listOperations()ontablesDB,documentsDB,vectorsDB,mysql,postgresql, andmongofor dedicated database lifecycle operationsVcsNamespace,VcsNamespaceList,DedicatedDatabaseOperation, andDedicatedDatabaseOperationListmodelsactivities.listEvents()takesqueriesasstring[]instead ofstringvcs.listRepositories()supportsequalon namespace in queriesstorage.listFiles()documentsfolderas a filterable attributepoints[]from a genuine zero valueNotes for reviewers
activities.listEvents()signature change.queriesgoes fromstringtostring[]. The old type was simply wrong — the endpoint has always taken an array server-side, so any caller passing a string was already getting a rejected request. No working code breaks; only code that could not have worked stops compiling. It is typed as a fix rather than a breaking change, consistent with 15.3.0–15.5.0 shipping outright method removals under minor bumps.Blocks the CLI release. appwrite/sdk-for-cli#346 (v23.2.0) currently fails
tscbecause it callslistInstallations,getInstallation,deleteInstallation,createInstallationToken,listOperations,listNamespaces, the 4-argumentcreateRepository, and the array-typedlistEvents— none of which exist in@appwrite.io/console@15.5.0. This release supplies all of them, and needs to be published to npm before the CLI can build.