fix: force release

[dsanders11]

• I have read the contribution documentation for this project.
• I agree to follow the code of conduct that this project follows, as appropriate.

Summarize your changes:

#1763 didn't trigger a release because the semantic prefix on the commit message got lost on merge, so forcing a release.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 89.08%. Comparing base (18b0c69) to head (bdaf4f5).
Report is 1 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #1764   +/-   ##
=======================================
  Coverage   89.08%   89.08%           
=======================================
  Files          17       17           
  Lines         907      907           
  Branches      187      187           
=======================================
  Hits          808      808           
  Misses         62       62           
  Partials       37       37           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[continuous-auth]

🎉 This PR is included in version 18.3.4 🎉

The release is available on:

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

Your semantic-release bot 📦🚀

[slashnick]

Oops, my bad. Thanks for triggering a release!

[dsanders11]

@slashnick, not your fault! We had a gap in our processes that caused it to slip through. 👍