A breaking change is a software update that changes behavior or an interface, so existing code that depends on it may stop working unless it is modified. Examples include removing a function, renaming a setting, changing what a function returns or dropping support for an older platform.

It matters because upgrades are not always free. A security fix that arrives together with a breaking change forces a choice between taking the fix and doing extra work to adapt. Release notes and deprecation warnings are the usual way maintainers signal that one is coming.

Whether something counts as breaking depends on how you use the software. A change that is harmless for one project can break another, and a project that follows a versioning scheme may still ship an unexpected break. A clean upgrade in testing does not prove that every code path is unaffected.

Before upgrading, read the changelog, pin versions so updates are deliberate, run your test suite and try the new version in a staging environment first. Where possible, upgrade in small steps rather than skipping many releases at once.