The important shift is that agent orchestration itself becomes a managed API surface: context compaction, tool discovery, programmatic tool calls and subagent coordination can now come from OpenAI’s maintained Codex harness rather than an application team rebuilding those layers.
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.
A six-month real-world comparison shows AI code-review agents and specialised fuzzers find substantially different V8 vulnerabilities. Replacing fuzzing with agents would leave gaps, and cost per bug remains unknown.
Computer Use is now GA in both Gemini APIs, but it is an action-planning tool, not a hosted remote desktop: clients execute clicks and keystrokes and must handle safety decisions.
Cloud CDN can now honor CDN-Cache-Control separately from browser-facing Cache-Control. That gives builders a standards-based way to set shared-cache behavior at the edge while preserving different client-side caching rules.
The endpoint names are staying the same, but the trust chain is not. Teams that pin Sentry certificates or still ship very old Android/Java runtimes need to remove or update those assumptions before Sentry publishes its exact February cutover date.
DeepSeek now charges for Search/Fetch calls made both directly and via DeepSeek Harness, Claude Code and Codex. Only successful nonempty 200 responses are billable.
The important change is enforcement. WordPress.org already had a release cooldown and automated scanning, but high-risk results can now stop a plugin update automatically instead of waiting for the Plugins Team to intervene.
Ada has added code tools that run a restricted Python subset inside agent conversations. They can transform API responses, perform deterministic calculations and call allowlisted domains, while MCP-authored changes can be staged and reviewed before promotion.
Builders can automate Stripe revenue and reconciliation analysis, but must plan for API permissions, asynchronous jobs, result retention and a February 2027 query-billing transition.
Wiz's rolling AI-platform security tracker has new vendor-confirmed incidents and a second Fireworks intrusion; NEAR's SGLang exploitation shows why confidential enclaves do not secure vulnerable inference software.
Sentry has completed a breaking alerting migration. Legacy alert APIs are gone; metric detection now lives in Monitors while notification routing lives in Alerts, and old direct integrations must use the replacement endpoints.
Ghost now stores typed member attributes with Portal self-service, CSV import and API updates. Publishers gain simpler segmentation, but cannot require fields or collect them at signup.
Repository growth tools can measure when star counts changed again without rebuilding individual-user histories. The new API deliberately separates aggregate popularity data from stargazer identity, so integrations need to distinguish trend analytics from user-level community data.
YepAPI corrected a platform-wide flat-rate billing defect on August 22 and left historical undercharges untouched. On the same date it also increased selected flat-rate and volume prices, making the current cost step-up larger for some endpoints than the billing fix alone would suggest.
The break is narrow but concrete: scripts and CI/CD calling the old route paths can fail, while monitoring code that expected `connections` inline must fetch it separately.
The deadline is no longer theoretical: browsers, Git HTTPS backends and API clients that still depend on SHA-1-era TLS algorithms can now lose connectivity to GitHub.com.
Mistral Large 4 now has explicit GA and hosted token pricing alongside downloadable weights; self-hosters must still check the model-service licence exception and actual serving costs.