[lohanidamodar]

Moves the browser SDK from 28.2.0-rc.7 to 29.3.0-rc.1 (npm next), pinned exactly.

In 29.3.0-rc.1 the tracker sends scroll_depth and engagement_time with interactive: false. Those events no longer end a bounce, so a visitor who only scrolls still counts as bounced.

28 → 29 breaking changes

29.0.0 breaks four things: the 2.5 response format, defaults filled into responses, nullable model fields typed T | null, and oauth2 resource params as string[]. None of them affect refetch. The browser SDK is used only in src/lib/appwrite-analytics.ts (Client, Analytics, Tracking) and src/lib/appwrite-browser.ts (Account, Avatars, ID, OAuthProvider.Appwrite). Neither file reads response models or calls oauth2, so no code changes are needed. functions/* and the server code use node-appwrite and are unchanged.

pnpm-workspace.yaml: the minimumReleaseAgeExclude entry now names the new RC instead of the old one.

Checks

• tsc --noEmit passes
• vitest run: 113 tests pass
• vite build passes
• prettier --check passes on the changed files
• I ran the real startAutoTracking / trackAppwriteEvent against the new SDK, with a stubbed DOM on a refetch.io host and fetch captured. It sent pageview, scroll_depth (interactive: false), engagement_time (interactive: false) and a custom vote event with its props, which has no interactive field.

[appwrite]

Refetch

Project ID: 63ef1792594ff4f50de2

Sites (1)

Site	Status	Logs	Preview	QR
App 688e6ad00039239f1ecc	Ready	View Logs	Preview URL

Functions (4)

Function	ID	Status	Logs
Readme	68a18eba0012c97a0017	Failed	View Logs
Scout	689bd7b6002c5d783925	Ready	View Logs
Algorithm	689b8b5f00075917c520	Ready	View Logs
Enhancement	6897c57600169dfb0b92	Ready	View Logs

Tip

Every Git commit and branch gets its own deployment URL automatically