Conventional commit prefixed with `fix!` did not result in a breaking change

[kaylareopelle]

The conventional commits guidelines state that anything that appends a ! after a type/scope should result in a breaking change. (source)

#1038 brought to our attention that a recent change that included fix!(instrumentation): as the commit type when merged into main but this was not applied. Instead, the changes were treated like fix:.

We expected to see BREAKING CHANGE listed in the Changelog. Since the gem is still at 0.x, a major version bump shouldn't occur.

[github-actions]

👋 This issue has been marked as stale because it has been open with no activity. You can: comment on the issue or remove the stale label to hold stale off for a while, add the keep label to hold stale off permanently, or do nothing. If you do nothing this issue will be closed eventually by the stale bot.