Blog posts from January 2026.
Upgrading a dependency sounds simple — until the new version renames an API, drops a feature, or changes default behavior. We explore how engineering teams at scale are building automated breaking-change detection into their upgrade workflows to move faster with less risk.
Peter ChapmanA single scan tells you where you are. Trend tracking tells you where you are going. Learn how to use vibgrate push, DSN tokens, and the Vibgrate dashboard to track drift across repositories, visualise trends over time, and give engineering leadership a portfolio view of upgrade health.
Luke GeavesUpgrading a dependency is easy — until it breaks your code. Vibgrate's Breaking Change Exposure scanner identifies deprecated packages, legacy APIs, and peer dependency conflicts before you start the upgrade, so you can scope the work accurately and avoid surprises.
Peter ChapmanBeyond the core drift score, Vibgrate runs a suite of extended scanners that collect migration intelligence. This post covers three of the most impactful: Platform Matrix, Dependency Risk, and Dependency Graph analysis — what they detect, why it matters, and how to use the output.
Luke GeavesSoftware Bill of Materials (SBOM) requirements are becoming standard — driven by regulation, customer contracts, and security best practices. Vibgrate can generate SBOMs in CycloneDX and SPDX formats directly from your drift scan, and compare two scans to show exactly what changed.
Peter ChapmanLocalStack's decision to discontinue its open-source Community Edition and require registration for its AWS emulator has sent ripples through the cloud-native development community. We examine the impact on migration workflows, CI pipelines, and the broader debate around open-source sustainability.
Luke GeavesA drift score is useful. A drift score that fails your build when it drops too low is transformative. Learn how to use --drift-budget and --drift-worsening to turn Vibgrate's drift scoring into an enforceable quality gate — a fitness function for your upgrade posture.
Peter ChapmanThe real power of drift scoring is not the one-off scan — it is the continuous signal. Adding Vibgrate to your GitHub Actions pipeline means every PR is checked for drift regression, every build knows its upgrade posture, and findings appear directly in your code review workflow.
Luke Geaves