Configure weighted traffic splits for Vercel Flags from the Vercel CLI

// related

• #0001

  #0001Infra & SaaSGitHub Changelog3 days ago

  Staged publishing and new install-time controls for npm

  70radar

  npm enhances supply-chain security with staged publishing and new --allow-* install flags. These features provide granular control over package sources, mitigating dependency attacks.

  • —staged publishing: Publish with npm publish --stage <name> and later promote with npm stage promote. This prevents accidentally tagging a pre-release as `latest`.
  • —--allow-* flags: New flags like --allow-file and --allow-remote let you explicitly whitelist installation sources during npm install, expanding on the existing --allow-git.
  • —Both features focus on hardening defenses against supply-chain attacks. It's a good practice to configure them in .npmrc even for solo projects with many dependencies.

  Source: github.blog/changelog/2026-05-22-staged-publishing-and-nRead original →
• #0002

  #0002Infra & SaaSGeekNews3 days ago

  `Railway` outage exposes GCP account-suspension blast radius

  50radar

  RailwayPaaS hosting platform — deploys apps and databases together

  A single cloud account suspension took down dashboard, API, compute, databases, control plane, and burst compute. Treat platform convenience as a dependency risk.

  • —The incident started on May 19, 2026 22:20 UTC and lasted about 8 hours. A hosted app needs an external status channel.
  • —Railway immediately returned 503 from both dashboard and API, so deploy and ops paths failed together.
  • —The failed surface included compute, database, control plane, and burst-compute infrastructure. Separate backup and recovery paths matter.

  Source: news.hada.io/topic?id=29740Read original →
• #0003

  #0003Infra & SaaSGitHub Changelog4 days ago

  `GitHub` Issue Fields Enter Public Preview for All Organizations

  60radar

  Typed metadata is now native on issues. Small teams can standardize triage without extra trackers.

  • —Priority, Effort, and similar typed fields can now live directly on GitHub issues, reducing custom labels and project-board drift.
  • —Public preview covers all GitHub organizations on github.com, so teams can test it without waiting for an enterprise rollout.
  • —GitHub Enterprise Cloud with data residency is included too; compliance-bound org repos get the same workflow option.

  Source: github.blog/changelog/2026-05-21-issue-fields-are-now-inRead original →