[Anmol-Baranwal]

Railway stops reading railway.toml files on Dec 1, 2026. This moves all 8 Outpost services to .railway/railway.ts, Railway's new config format, and removes the old railway.toml files.

What's in it

• Same Dockerfile, restart and healthcheck settings as each service had before
• Production builds from main, staging from staging
• Waits for CI before deploying, same as now
• slack-bot, teams-bot and linear-sync stay manual deploy only
• The release bot runs in production only
• Deployment docs and the release bot README now point to railway.ts

Safety

• The file only manages these 8 services, so it never touches the Postgres databases
• It refuses to apply in an environment until that environment's variables are copied in, so secrets can't be wiped

Before merging (needs Railway access)

Keep this as a draft until then. The services still read the old files, so merging early breaks their next deploy.

1. Run railway config pull for staging and production, and copy the variables into .railway/railway.ts
2. Merge, then in the same sitting clear each service's config file path in Railway
3. Run railway config plan and check it removes nothing
4. Run railway config apply

Full steps are at the top of .railway/railway.ts.