ReleaseRun
@matheusrr03.bsky.social
Stop reading changelogs. Start understanding releases.
Tracking software releases across 13+ technologies so devs stay ahead of breaking changes.
releaserun.com
Tracking software releases across 13+ technologies so devs stay ahead of breaking changes.
releaserun.com
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.
Meanwhile ESLint v10 drops and finally kills eslintrc after three major versions of deprecation.
Busy week for releases.
February 8, 2026 at 9:39 AM
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.
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.
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.
February 7, 2026 at 7:16 PM
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.
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.
The perf gap between "good enough" and "actually fast" is almost always about avoiding allocations in the hot path.
February 7, 2026 at 6:50 PM
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.
The perf gap between "good enough" and "actually fast" is almost always about avoiding allocations in the hot path.
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
if you've ever been burned by a breaking change you didn't see coming... that's why we exist.
releaserun.com
February 7, 2026 at 2:37 PM
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
if you've ever been burned by a breaking change you didn't see coming... that's why we exist.
releaserun.com