Bump appwrite version

[vermakhushboo]

What does this PR do?

Bump appwrite version

Test Plan

(Write your test plan here. If you changed any code, please provide us with clear instructions on how you verified your changes work.)

Related PRs and Issues

(If this PR is related to any other PR or resolves any issue or related to any issue link all related PR and issues here.)

Have you read the Contributing Guidelines on issues?

(Write your answer here.)

Summary by CodeRabbit

• Chores
  • Updated Appwrite backend service dependency to a newer version.

[coderabbitai]

Walkthrough

This pull request updates the Appwrite dependency in package.json from version ^17.0.0 to ^21.2.1. This is a major version bump spanning four minor versions. No code modifications are present in the diff, and no exported or public declarations were altered. The change is isolated to a single dependency version specification.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~12 minutes

Rationale: While the diff itself is trivial (a single version number change in one file), the review complexity stems from the significant version jump (17.x to 21.x). A reviewer should verify Appwrite's breaking changes between these versions, confirm API compatibility with existing code, and ensure the application functions correctly with the new version. No direct code logic review is required since no application code was modified.

Pre-merge checks and finishing touches

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Docstring Coverage	⚠️ Warning	Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%.	You can run @coderabbitai generate docstrings to improve docstring coverage.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title Check	✅ Passed	The pull request title "Bump appwrite version" directly and accurately describes the main change in the changeset, which is updating the appwrite dependency from ^17.0.0 to ^21.2.1 in package.json. The title is concise, clear, and uses straightforward language that would allow a teammate scanning the history to immediately understand the primary purpose of this change without ambiguity or vagueness.

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch chore-bump-appwrite-version

---

📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 16aa2d1 and 18df49d.

⛔ Files ignored due to path filters (1)

• package-lock.json is excluded by !**/package-lock.json

📒 Files selected for processing (1)

• package.json (1 hunks)

🔇 Additional comments (2)

package.json (2)

1-66: PR description lacks critical detail for dependency version bump.

The PR body is minimal and doesn't provide:

• Motivation: Why bump to v21.2.1? (security patch, bug fix, feature requirement?)
• Breaking changes: Are there API changes requiring code updates?
• Test plan: What testing was performed?
• Migration notes: Any special steps for this version jump?

For dependency updates spanning multiple major/minor versions, include detailed commit messages and test evidence to help reviewers assess risk and validate compatibility.

---

25-25: I need to refine the search to be specific about the SDK type. Let me search for breaking changes in the Appwrite JavaScript/TypeScript SDK specifically:

Now let me search for more specific information about the SDK compatibility and version support:

Based on my verification, the concerns in the original review comment are partially substantiated by the Appwrite documentation and release practices, though the risk profile is somewhat lower than initially suggested. Here is the rewritten comment:

---

Validate the SDK bump and document any required code changes.

While Appwrite SDKs maintain backward compatibility with the Appwrite APIs and applications should continue working after upgrade, you must check the changelog to understand what SDK-level changes have been made and what adjustments are required.

The jump from v17 to v21 is significant. Before merging:

1. Confirm SDK compatibility: Verify that react-native-appwrite@^0.7.0 (line 44) is compatible with the new appwrite@^21.2.1 and review the JavaScript SDK v21 changelog for method signature or parameter changes.
2. Test the changes: Add evidence of testing with the new version—this is essential for any major SDK bump.
3. Document findings: Update the PR description to explain what motivated this bump (feature, security patch, bug fix, maintenance) and confirm all code continues to work as expected.

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}