Retool quietly killed self-hosted pricing. No announcement, just a silent docs update.
If a vendor's revenue model needs you NOT to self-host, that option is always temporary.
just saw someone got llama 70B running on a single RTX 3090 by streaming weights from NVMe straight to GPU, bypassing CPU entirely. consumer hardware doing what needed a cluster a year ago. the inference speed tradeoff is real but the approach is clever as hell.
Go 1.26 shipped and the Green Tea GC is now default — 10-40% GC overhead reduction in real workloads. Also goroutine leak detection via runtime/pprof, which is huge for production debugging. And 30% faster cgo calls. Solid release.
Python 3.9 and Node.js 18 both hit EOL in April 2026. Two of the most-used runtimes dying simultaneously.
If your CI pins either, you have ~8 weeks. Skip Python 3.10 entirely (EOLs Oct 2026). Go straight to 3.12+.
K8s 1.33 follows in June. Brutal quarter.
The biggest risk of vibe coding isn't bad code — it's invisible dependency debt.
LLMs pick your deps. You don't understand why. 6 months later half are EOL with CVEs, and upgrading is harder than rewriting.
The flow state feels productive. The maintenance bill arrives later.
K8s 1.35 quietly removed cgroup v1. Kubelet won't start on v1 nodes.
This won't show up in CI — it shows up at 2am when your node pool upgrade rolls and pods stop scheduling.
Check before upgrading:
stat -fc %T /sys/fs/cgroup
(needs cgroup2fs)
#Kubernetes #DevOps
Node.js 20 reaches EOL in 77 days. If you're still running it in prod, start testing 22 LTS now — not when security patches stop.
Biggest surprise in the jump: TLSSocket now has a default error handler. Code silently swallowing TLS errors will behave differently.
Matrix is gaining ground in government IT (replacing Slack/Teams) and it makes total sense. Self-hosted, end-to-end encrypted, open protocol. The real story is how many orgs are quietly moving away from SaaS chat tools for security reasons. Decentralization is winning where it matters most.
Mitchell Hashimoto open-sourced Vouch — trust management for OSS repos. Contributors need explicit vouches from trusted members before PRs land.
Solving AI-generated drive-by PRs. The web-of-trust model where projects share vouched lists is the interesting part.
Submitted 10 URLs to Google Search Console today. 4 of them had never been crawled.
3-month-old domain. 85 pages. 1 indexed.
SEO from zero is humbling. Every signal matters — sitemaps, internal links, backlinks, manual submissions. No shortcuts.
Both Trivy and Grype trending on GitHub today — two container vulnerability scanners in the top 25 at the same time.
Meanwhile ESLint v10 drops and finally kills eslintrc after three major versions of deprecation.
Busy week for releases.
Trivy v0.69.1 just dropped - patching CVEs in its own Alpine base and Go runtime.
A vuln scanner patching its own vulns. Peak security. But this is what good looks like: fast patch cycles, transparent changelogs.
Your CI scanner should update as fast as the vulns it finds.
TIL most of Pino's speed advantage in Node.js comes from sonic-boom (batched async I/O) and hand-built JSON strings instead of JSON.stringify.
The perf gap between "good enough" and "actually fast" is almost always about avoiding allocations in the hot path.
expo honestly has some of the best release notes in the ecosystem. clear migration guides, actual context about why things changed, not just a list of commit hashes. more projects should take notes (pun intended)
renovate bot with grouped PRs has been the move for us. batch minor/patch updates weekly, flag majors separately for manual review. the key is actually reading what changed before merging though — blindly auto-merging patch updates has bitten me more than once
the nested dependency audit loop is truly one of the circles of hell. "just override it" they say, until three months later you discover the override masked a real vulnerability and now you have bigger problems
hey, i'm Matheus 👋 dev working on ReleaseRun — we track software releases across 13+ technologies so you don't have to dig through changelogs to figure out what actually changed.
if you've ever been burned by a breaking change you didn't see coming... that's why we exist.
releaserun.com
