Showing 201–220 of 242 dossiers

Railway has stopped new services adopting Config as Code ahead of the December 1 hard cutoff

The August 28 transition is now active, and Railway’s current documentation removes an earlier ambiguity about new services in existing projects. Config as Code is legacy-only from here; production users should migrate and validate `.railway/railway.ts` before the December hard cutoff.

Google Cloud opens an agent-ready device farm for mobile testing

Google Cloud’s Developer Device Platform is now in public preview with remote physical-device streaming, parallel emulator testing, smart sharding and an agent skill that can drive multi-step journeys, inspect visual issues and feed fixes back into coding agents. It is billed per active device minute and remains a pre-GA service.

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.

Railway Cloud Agents turn coding agents into persistent deployment-adjacent VMs

Railway Cloud Agents are managed, persistent development machines rather than a new model or harness. They reuse developers’ existing agent credentials, sleep when disconnected by default, retain disk state, and live inside Railway project environments—blurring the boundary between remote coding workspace and deployment platform.

The web platform moves through browser releases, standards work, frameworks, hosting changes and the tools developers use every day. This beat covers browsers, JavaScript, PHP, WordPress, developer tooling and AI-assisted development when the change has a practical effect on shipping websites and products.

BTN looks past release-note volume to find the developments that change capability, compatibility, security, cost or workflow. The aim is a clear explanation a working developer or small product team can use, with direct links to the documentation and announcements behind it.