`GitHub` Issue Fields Enter Public Preview for All Organizations

// related

• #0001

  #0001Infra & SaaSvercel_blog10 hours ago

  `Vercel CLI` Can Now Pull Anomaly Alert Details

  60radar

  Anomaly status now reaches the terminal, including AI investigation output with --ai. Useful for incident triage, but gated behind Observability Plus.

  • —vercel alerts lists team or project alerts with start time, alert type, and active status; terminal triage gets less context-switching.
  • —--ai adds AI investigation results next to each alert, giving coding agents enough context to act from the CLI.
  • —Availability is limited to Observability Plus, so the value depends on whether observability spend is already justified.

  Source: vercel.com/changelog/pull-anomaly-alert-details-using-thRead original →
• #0002

  #0002Infra & SaaSvercel_blog12 hours ago

  `Qwen 3.7 Max` lands on `Vercel AI Gateway`

  70radar

  Qwen 3.7 MaxLLM — built for coding and long-horizon agents

  Alibaba’s agent-focused model is now callable through the AI SDK. Routing, retries, cost tracking, and BYOK make it worth a quick prototype test.

  • —Use model ID alibaba/qwen-3.7-max; existing AI SDK paths can compare it without provider-specific wiring.
  • —Positioned for coding, office workflow automation, and long-horizon autonomous execution. Add it to multi-file engineering bake-offs.
  • —Gateway features include usage and cost tracking, retries, failover, and intelligent routing. One API reduces provider-switching overhead.
  • —Built-in BYOK, observability, and custom reporting keep model experiments easier to measure across small products.

  Source: vercel.com/changelog/qwen-3-7-max-now-available-on-verceRead original →
• #0003

  #0003Infra & SaaSGeekNews18 hours ago

  `Railway` Outage Resolved After `Google Cloud` Account Block

  50radar

  RailwayPaaS hosting platform — Git-based app deploys

  A provider-level account block took the platform down broadly. Treat hosted PaaS as a dependency with vendor lockout risk, not just runtime uptime.

  • —Users hit no healthy upstream, unconditional drop overload, login failures, and dashboard access failures — control plane and runtime both degraded.
  • —The cause was a Google Cloud account block, so the failure sat below Railway’s own app layer. Status pages alone do not cover this risk.
  • —For revenue apps, keep DB backups, DNS escape routes, and deploy docs outside the platform. Recovery speed depends on prewritten exits.

  Source: news.hada.io/topic?id=29725Read original →