feat: React Native SDK update for version 0.34.0#111
Conversation
Greptile SummaryThis PR updates the React Native SDK to version 0.34.0, adding new authentication, query, and model features generated from the latest Appwrite API spec. Dependency tooling is also updated and npm overrides are added to pin transitive dependencies to secure versions.
Confidence Score: 5/5This PR is safe to merge — all changes are additive (new methods, new enum value, new optional model fields) with no modifications to existing behavior. The new setBearer method correctly includes the Bearer scheme prefix. The three vector query methods follow the established array-wrapping serialization pattern used consistently by all other geometric queries in the file. The new Locale fields are all optional, keeping the type change backward-compatible. Dependency overrides are development-only and do not affect downstream consumers of the SDK. No files require special attention. Important Files Changed
Reviews (2): Last reviewed commit: "chore: update React Native SDK to 0.34.0" | Re-trigger Greptile |
| - name: Install dependencies, audit, and build | ||
| run: | | ||
| npm ci | ||
| npm audit --audit-level=high --omit=dev |
There was a problem hiding this comment.
Failing audit blocks the entire publish workflow
Running npm audit --audit-level=high as a hard prerequisite of publishing means any newly-disclosed high-severity CVE in a transitive production dependency will block all releases until patched, even for unrelated emergency fixes. Consider running the audit as an informational step or in a separate job with continue-on-error: true.
Prompt To Fix With AI
This is a comment left during a code review.
Path: .github/workflows/publish.yml
Line: 40
Comment:
**Failing audit blocks the entire publish workflow**
Running `npm audit --audit-level=high` as a hard prerequisite of publishing means any newly-disclosed high-severity CVE in a transitive production dependency will block all releases until patched, even for unrelated emergency fixes. Consider running the audit as an informational step or in a separate job with `continue-on-error: true`.
How can I resolve this? If you propose a fix, please make it concise.Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!
This PR contains updates to the SDK for version 0.34.0.
What's Changed
Client.setBearer()method for OAuth access token authenticationQuery.vectorDot,Query.vectorCosine, andQuery.vectorEuclideanvector similarity queriesAppwritevalue to theOAuthProviderenumcity,timeZone,latitude,isp, etc.) toModels.Locale