I’m not sure what the policy is around editing release notes for defold, but this is one of the top articles when you search for “box2d defold”:
…and it doesn’t mention that triggers are completely unreliable in box2d 3.0 in defold. It would be good to note that somewhere prominent - a warning in the UI itself would be even better.
Because most of box2d 3.0 works as expected, I upgraded as a distinct step, tested everything, everything seemed fine, and then I kept working. Later, the randomness of trigger events described in that issue caused a subtle bug that was very hard to track down to the box2d update, since the behavior is non-deterministic and works in some playthroughs but not in others.