Know what breaks before you run docker compose pull.
Automated continuous update intelligence for self-hosted apps, homelabs, and private cloud infrastructure. We analyze changelogs, post-release issue spikes, schema migrations, and community reactions to tell you whether upgrading is safe or will break your setup.
Tracks GitHub issues opened strictly after publication timestamp to surface early crashes, UI freezes, and breaking regressions.
Detects irreversible database schema updates, removed configuration environment flags, and deprecated API contracts before you apply them.
Every report provides ready-to-run Docker CLI commands and Compose tags to immediately pin and restore your previous stable version (N-1).
Privacy fix disabling ML telemetry with no migrations or breaking changes; only 1.8 hours of data, so monitor the Android widget crash report.
Feature-heavy release with zero negative reactions, but a Milvus duplicate-chunk bug and search race condition warrant caution for knowledge-base users.
Mostly fixes, but OpenAI-compatible sampler defaults changed and cloud /api/usage reportedly dropped percentage fields. Validate client integrations before upgrading production.
Early reports show regressions in person loading, Alexa rate limits, and renamed devices; wait 48-72 hours before upgrading production.
Mostly device additions, but ConBee III startup regression and Aqara blind position bug reported; hold on coordinator setups until fixed.
Bug-fix-only release with positive early reactions, but only 1.3 hours old with no issues yet. Wait a few days before upgrading production.
Minor bugfix release updating .NET to 10.0.14. Four post-release issues, including a 12.4-specific music player library reload regression. Wait for more reports before upgrading.
No issues in 46 hours, but telemetry is thin (3 reactions). Changelog not reviewed; verify migration and config notes before upgrading production.
Too early to judge; security fixes make prompt update advisable, but back up first and validate config, since invalid settings now block startup.
Low-risk patch updating the Alpine base image and CI caching. No breaking changes or issues yet, but only 3 hours of data.
Security-focused Go and dependency update with low-risk changes, but a possible Go-related CLI updater resolution regression (#8689) needs verification before upgrading.
Safe-looking patch with security fixes and no reported regressions; upgrade reasonably. Rate-limit bypass report concerns v3 beta, not this release.
Critical security release with a breaking TLS trust change: verify OAuth, LDAP, registry, and Git endpoints don't use eMudhra certificates before upgrading. Kubeconfig tokens are now scoped to Kubernetes proxy routes.
Mature release with strong reception, but certbot 5.8.0 may break DNS plugins and an upgrade pull failure is reported. Back up before upgrading.
Mostly bug fixes and dependency bumps, but only 2.7 hours of data. Read the migration guide before upgrading, and wait for more community feedback.
Everything you need to know about DidItBreak automated stability tracking.
Our engine correlates release timestamp with GitHub REST telemetry. We weigh the volume and severity of newly opened bug issues, official changelog breaking changes, database migration requirements, and community sentiment (positive vs negative reactions) to generate an actionable score from 1 to 10.
Blind auto-updates frequently break self-hosted instances when software introduces breaking changes (such as authentication overhauls, database schema migrations, or removed volume mappings). DidItBreak helps sysadmins determine whether a release is production-ready or needs a backup prior to pulling.
The radar continuously scans monitored repositories every 4 hours. Fresh releases under 48 hours old are prioritized to catch emergent community reports before you upgrade.
Every app detail page includes an Emergency Rollback section. You can copy the exact Docker CLI command or compose tag to pin your container back to the previous stable (N-1) release immediately.