Self-hosted Supabase now defaults to Envoy instead of Kong
Supabase’s self-hosted stack now routes through Envoy by default, bringing new API-key support and hardened gateway defaults while breaking some Kong-specific assumptions.
Search
Search results for “AI SDK HarnessAgent”
Find published research by company, product, platform or technology.
Showing 121–127 of 127 dossiers
Bun 1.4 rewrites the runtime in Rust and moves closer to Node.js 26 compatibility
Bun 1.4 combines an implementation-language rewrite with a larger built-in standard library and a substantial Node-compatibility push. For teams already running Bun, the practical task is to validate native addons, runtime behavior and workload-specific performance rather than treating this as a drop-in minor upgrade.
Twilio now blocks new Toll-Free messaging verifications without public privacy and terms URLs
A previously preparatory compliance field is now an operative delivery gate. Builders automating Toll-Free onboarding need to collect, validate and submit policy URLs as part of registration rather than treating them as optional metadata.
TikTok has retired HTML mini games — developers must rebuild them for its native runtime
This is a platform migration with a real rewrite boundary. Existing HTML games need to be rebuilt through Unity, Cocos or Laya, then have login, ads, purchases and other TikTok capabilities reintegrated and retested before relaunch.
LinkedIn is sunsetting the Profile API `location` field in favor of `geoLocation`
This is separate from LinkedIn’s Ads Legacy Geo cutoff already tracked by BTN. Profile and compliance integrations can fail more quietly: the request may still succeed while a field the application expects simply disappears or becomes null.
Web DevelopmentMarketing & DistributionEmail & LifecycleDeveloper ToolsConversion & AnalyticsActive dossier
Amazon SES can now switch open and click tracking per email request
The new request-level controls make email measurement a per-send decision: an application can keep one SES configuration set while disabling open or click tracking for recipients who should not be measured. The override wins over the configuration-set default and adds no separate feature charge.
Render decouples memory from CPU with new compute plans up to 96GB RAM
Memory-bound agents, retrieval systems and stateful services can now choose 2-, 4-, 8- and 12-CPU Render plans with much wider RAM ratios. Existing plan prices and legacy IDs stay compatible; the new choices change the cost trade-off for workloads that previously had to overbuy CPU to get enough memory.