api versioning: when to break compatibility?

hey evryone, ive been thinking a lot about api versioning lately, esp for services that are always evolving. weve all seen the pain of breaking changes. whats your teams general approach to versioning? do you lean toward semantic versioning strictly, or do you have specific triggers for introducing a new major version? im curious about the trade offs youve found between maintaining backward compatibility and the freedom to innovate quick