Scale containers up or down with a stepper, right from the project card

Each container card in a project's Containers tab now has a +/- stepper next to the instance count, letting you scale a container up or down directly, without a new deployment. While the running count hasn't caught up with the target yet, the card shows a hint like "2/3 active".
The maximum number of instances per container depends on your plan: 1 on Free, 2 on Starter, 5 on Pro, 15 on Business, with an absolute ceiling of 50 instances regardless of plan. Past your plan's quota, the stepper opens an upgrade dialog instead of scaling further.

The managed Postgres/Redis env vars injected into your containers have been renamed to be engine-agnostic: PGHOST/PGPORT/PGDATABASE/PGUSER/PGPASSWORD are now DATABASE_HOST/DATABASE_PORT/DATABASE_NAME/DATABASE_USER/DATABASE_PASSWORD, and REDIS_HOST/REDIS_PORT/REDIS_URL/REDIS_PASSWORD are now CACHE_HOST/CACHE_PORT/CACHE_URL/CACHE_PASSWORD (DATABASE_URL is unchanged). If your app code reads the old names directly, update it and redeploy.

Project backups were silently failing whenever a project had unlinked its managed database: the backup kept targeting a stale, no-longer-relevant Postgres container instead of skipping straight to a volumes-only backup.