This is a breaking change because error type returned in case of acquire timeout is changed, can't be backported

I don't mind too much as we need to run a fork anyway, but that sounds like an overly strict interpretation of semver. I wouldn't consider a different error class being thrown as enough of a breaking change to delay an important fix to the next major release.

This is an important fix but returning different Error class entirely for some condition is definitely a breaking change. User could be catching old TimeoutError and retrying transactions.

There is still a way to make this change non breaking, you can just include transaction.js changes which prevent rollback in case of no connection. I'll happily merge that change :)

Codecov Report

Merging #9889 into v4 will increase coverage by <.01%.
The diff coverage is 100%.

🎉 This PR is included in version 4.38.1 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀