<Summarize the change in imperative mood>

<What changed and why compatibility could not be preserved>

Migration:
<Steps users or dependent code must take to upgrade>

BREAKING CHANGE: <What stops working, and for whom>

# Keep "BREAKING CHANGE:" in uppercase at the start of the last
# paragraph so release tools can detect it.
# Using Conventional Commits? Add ! to the subject: feat(api)!: ...
