What is a common mistake when working with backward-compatible API changes?

A common mistake with backward-compatible API changes is assuming clients ignore unknown behavior or can instantly adopt a renamed field often causes production breakage across independently deployed consumers. The safer approach is to design and test the behavior explicitly rather than assuming the platform or dependency will handle it automatically.