May product update: Presences API, Rust runtime, 7x faster Storage uploads, and more

[aishwaripahwa12]

May product update blog

[appwrite]

Appwrite Website

Project ID: 69d7efb00023389e8d27

Sites (1)

Site	Status	Logs	Preview	QR
website 69d7f2670014e24571ca	Building	View Logs	Preview URL

Website (appwrite/website)

Project ID: 684969cb000a2f6c0a02

Sites (1)

Site	Status	Logs	Preview	QR
website 68496a17000f03d62013	Queued	View Logs	Preview URL

---

Tip

Preview deployments create instant URLs for every branch and commit

[greptile-apps]

Greptile Summary

This PR adds the May 2026 product update blog post covering Presences API, Rust runtime, parallel Storage uploads, database relationships GA, BigInt columns, Git deployment triggers, deployment retention, email policies, Bun/Deno build runtimes, Dart/Flutter version bumps, and the OpenAI Codex plugin — along with 13 accompanying .avif images.

• The markdoc file uses correct ![alt](path) image syntax with .avif extensions throughout, the aishwari author slug resolves to an existing author page, and the Codex cover image reuses a valid asset from the existing announcing-appwrite-codex-plugin image directory.
• Seven [Read more] / [Read the announcement] links target blog posts not yet present in the repository (announcing-presences-api, relationships-are-out-of-beta, faster-storage-uploads-parallel-chunks, announcing-git-deployment-triggers, announcing-dart-flutter-runtimes, building-snapchat-clone-with-presences-and-realtime, kimi-k2-6-arena-leaderboard-refresh); if this post is deployed before those are merged, all seven CTAs will return 404s.

Confidence Score: 4/5

Safe to merge only if the seven referenced announcement posts land simultaneously or are already live; merging this post first leaves multiple broken CTAs visible to readers.

The post itself is well-formed — images, author, and frontmatter are all valid. The risk is deployment ordering: seven internal links point to blog posts that don't yet exist in the repository. If this update post goes live before those individual posts are merged, every one of those "Read more" links returns a 404. The fix is straightforward (coordinate merge order or deploy together), but the issue is real and user-facing.

src/routes/blog/post/may-product-update-presences-api-rust-runtime-7x-faster-storage-uploads-and-more/+page.markdoc — verify all linked announcement posts are merged before or alongside this one

Important Files Changed

Filename	Overview
src/routes/blog/post/may-product-update-presences-api-rust-runtime-7x-faster-storage-uploads-and-more/+page.markdoc	New May product update blog post; 7 internal "Read more" links point to blog posts not yet in the repository, which will 404 if this post ships first
.optimize-cache.json	Auto-generated image optimization cache updated to include new blog post images
bun.lock	Lock file updated; no changes of concern for a content PR

_{Reviews (4): Last reviewed commit: "Merge branch 'main' into may-product-upd..." | Re-trigger Greptile}