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.
Search Console can now treat supported social and video accounts as properties, exposing Google impressions, clicks, queries and post-level performance for Instagram, TikTok, X and YouTube content.
The September 17 GA changes the economics of Neon's backend: free allowances remain, but object storage, function execution and model calls are now metered on paid plans. November 2 adds an OAuth Provider plugin, still labelled beta.
MiMo-V2.6 is more useful than another benchmark launch because builders get both capable multimodal weights and a rare view into the reinforcement-learning machinery that produced them: code, environments, run costs and even failure notes from the training cluster.
Fin Releases and Evals are now generally available across Intercom workspaces, giving support teams a repeatable preview, test and staged-rollout process for changing AI agent behaviour.
The November 16 Search Analytics API update unlocks brand and multimodal reporting for developers, with eligibility, historical coverage and client-library caveats.
Preact's long-awaited major release brings concrete rendering changes and a packaging break. Most modern projects should migrate easily, but old import paths and CommonJS tooling need attention.
Modern Web Guidance 1.0 adds Baseline-aware agent skills and a limited legacy scanner. Independent tests show useful fixes alongside substantial blind spots and higher agent costs.
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.
CVE-2026-105445 moved personal access tokens across Docker Hub identities without rotating their secrets. Affected users were notified and tokens deactivated after the September 30 fix, but the two-year exposure illustrates a container supply-chain trust boundary.
CLM-8B targets the same narrow decision layer as Jev, but with open weights, local deployment and a contrastive architecture that separates state and action representations. The headline speed and coding results are researcher-produced and need careful interpretation.
The architecture matters as much as the voice quality: developers can replace a chained speech-to-text → LLM → text-to-speech loop with one full-duplex conversational model while keeping their own choice of backend reasoning model, tools and agent harness.
Search Console now separates both generative-AI visibility and multimodal image-led searches, giving publishers a clearer first-party view of how content is discovered outside conventional typed queries.
v5 gives DigitalOcean users a more composable VM shape instead of choosing only from fixed bundles, with vendor-claimed per-core performance gains up to 30%. The billing model deserves equal attention: long-running v5 instances do not inherit a monthly usage ceiling.
Stacked pull requests are now generally available on GitHub. The shift matters as coding agents make large changes faster than humans can safely review them: teams can keep one coherent change dependency-ordered while reviewing it as smaller PRs.
Investigations has crossed from preview into production and incident.io now reports a large latency improvement in its own measured workflow. The agent continuously reassesses evidence and can hand remediation to coding agents, but the new speed and accuracy figures remain vendor-produced rather than independent.
Android Bench 2.0 moves coding-agent evaluation away from small repository fixes toward dependency upgrades, app builds, migrations and other jobs that can take a human engineer days. The results expose a much larger reliability gap than short-task benchmarks—and show that the agent harness can materially change cost and outcome.
The median SaaS LTV forecast looks almost right at 12 months, but that average hides huge misses in both directions. For acquisition budgets, payback planning and company valuation, ChartMogul’s new 3,331-company analysis argues for treating LTV as a directional indicator rather than a precise revenue forecast.