The new tracing path gives Supabase requests a shared trace_id across browser or app spans and backend logs, with support for OpenTelemetry-compatible tooling. For JavaScript users, the practical detail is a required upgrade to supabase-js 2.112.0 or later because 2.106.0 through 2.111.x silently failed to propagate headers in bundled applications.
Shopify’s August 26 deadline is a concrete compatibility cutoff for non-Plus stores. Legacy Thank you and Order status customizations must be rebuilt with supported blocks, web pixels or app pixels, or the automatic upgrade can break analytics and post-purchase behavior.
GitHub Spark stops being available to existing users on August 31, 2026. Deployed apps are meant to keep running, but owners should export code to a repository now; Spark apps using `llm()` need a separate inference provider because the underlying GitHub Models service retired July 30.
Agent Plugins 1.0 now has documented support across VS Code, Cursor, GitHub Copilot, ChatGPT/Codex, Kiro and several open-source agents. That makes the format materially more useful for cross-client distribution, but portable components remain limited to Agent Skills and MCP servers while permissions, hooks, commands and host UX stay client-specific.
GitHub OAuth apps can now use eight-hour access tokens with rotating refresh tokens, register up to 10 callback URLs, and explicitly control wildcard callback matching. New apps default to expiring tokens, while existing single-callback apps should review a legacy wildcard setting GitHub has now made visible.
Gemini 3.7 Flash is now generally available with a 1M-token context window, tunable reasoning, stronger coding and agentic performance, and introductory API pricing of $0.75 per million input tokens and $3.75 per million output tokens through December 31, 2026.
Published Updated 8 min read
Developer tools shape the speed and confidence of daily work. Editors, terminals, build systems, testing tools and repository services can remove friction, but a new layer can also add lock-in, security exposure or another system a team must understand.
This page follows tools that materially alter how software gets made, including AI-assisted workflows when the development is primarily about developer practice. BTN looks beyond feature lists to setup cost, interoperability, data access and behaviour on real projects. The goal is to help builders spot improvements worth adopting while keeping control of the code, credentials and production systems those tools can reach.
Maintenance matters as much as launch velocity. BTN watches export paths, file formats, extension ecosystems and whether a company can change terms around work a developer already depends on. Tools should earn a place in the workflow through sustained usefulness, not simply through an impressive first session.