🧪 Tech & Open Source
Kubernetes API Deprecations
Official⏱ Weekly digest, Wednesdays
Every Kubernetes upgrade starts with the same ritual: digging through the deprecation guide to figure out which APIs vanish in the next version. This watch tracks removals and support windows against the version you actually run, so nothing gets removed out from under your manifests.
- Suggested cadence
- Weekly digest, Wednesdays
- Typically watches
- Kubernetes release notes · EKS documentation · CNCF blog · SIG announcements
- Tags
- kubernetes · deprecations · eks · devops
The prompt
We run three EKS clusters on Kubernetes 1.31 for a logistics platform in the US. Alert me when a new Kubernetes minor version announces API removals or deprecations that affect workloads on 1.31 through 1.33, and whenever AWS publishes or changes EKS end-of-support dates for those versions. Must name the removed API group and version and the replacement. Helm chart incompatibilities for ingress-nginx and cert-manager are a bonus.
This is the whole template — the words the wizard analyzes into sources, filters, and a schedule. You review and edit every step before the watch runs.
More like this
Critical CVEs in My StackOfficial
Know within hours when a critical CVE lands in something you actually run.
I run Node.js 22, PostgreSQL 16, nginx 1.26, and Ubuntu 24.04 in production. Alert me on any new CVE affecting those exact components with a CVSS score of 8.0 or higher, or anything added to the CISA KEV list regardless of score. Every alert must name the affected version range and the patched version or a workaround. A public proof-of-concept exploit makes it urgent, flag that separately. Ignore advisories for components I don't run.
⏱ Every 2 hours
Frontier Model LaunchesOfficial
Every new frontier model with pricing and context window, the day it ships.
I build LLM products and need to know about every new model release from OpenAI, Anthropic, Google DeepMind, Meta, and Mistral. Must include the API pricing per million tokens and a context window of at least 128k, otherwise it's not relevant to my work. Open-weights releases are a bonus and so are published benchmark comparisons against the previous generation. Skip minor version bumps and region-only rollouts.
⏱ Twice a day
React and Next.js Upgrade RadarOfficial
Breaking changes and codemods for your React stack, before you hit them in CI.
My remote product team maintains four apps on Next.js 15 and React 19 with the App Router. Alert me on every new stable major or minor release of React or Next.js that includes breaking changes, deprecations, or changed defaults. Each alert must summarize what breaks and whether an official codemod covers it. RFCs that affect the App Router or Server Components are a bonus. Ignore canary and experimental releases entirely.
⏱ Weekly digest, Mondays