Skip to content

feat: React Native SDK update for version 0.34.0 #111

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
ChiragAgg5k merged 2 commits into from
Jul 13, 2026
Merged

feat: React Native SDK update for version 0.34.0 #111

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
a87d96a
chore: update React Native SDK to 0.34.0
ChiragAgg5k Jul 13, 2026
fea8440
chore: update React Native SDK to 0.34.0
ChiragAgg5k Jul 13, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 2 additions & 1 deletion .github/workflows/publish.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -34,9 +34,10 @@ jobs:
echo "tag=latest" >> "$GITHUB_OUTPUT"
fi

- name: Install dependencies and build
- name: Install dependencies, audit, and build
run: |
npm ci
npm audit --audit-level=high --omit=dev

@greptile-apps greptile-apps Bot Jul 13, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 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!

Fix in Claude Code Fix in Codex

npm run build

- name: Publish
Expand Down
8 changes: 7 additions & 1 deletion CHANGELOG.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,10 +1,16 @@
# Change log

## 0.34.0

* Added: `Client.setBearer()` method for OAuth access token authentication
* Added: `Query.vectorDot`, `Query.vectorCosine`, and `Query.vectorEuclidean` vector similarity queries
* Added: `Appwrite` value to the `OAuthProvider` enum
* Added: optional geolocation fields (`city`, `timeZone`, `latitude`, `isp`, etc.) to `Models.Locale`

## 0.33.0

* Added: Realtime connections now send the configured JWT for authentication.
* Added: Forwarded `impersonateUserId` on `avatars` and `storage` file requests.
* Fixed: URL-encode path parameters across all services.

## 0.32.0

Expand Down
Loading