fix: force release

[angeloashmore]

Resolves:

Description

Force a release to include the latest chore dependency upgrades in a published version.

Checklist

• A comprehensive Linear ticket, providing sufficient context and details to facilitate the review of the PR, is linked to the PR.
• If my changes require tests, I added them.
• If my changes affect backward compatibility, it has been discussed.
• If my changes require an update to the CONTRIBUTING.md guide, I updated it.

Preview

How to QA ¹

---

Note

Low Risk
No code changes are present in the diff, so runtime and behavior risk is effectively none; the only impact is procedural (triggering a release).

Overview
This PR contains no code changes (empty diff), and appears intended solely to force a release so previously merged dependency upgrades can be published.

^{Written by Cursor Bugbot for commit d27903a. This will update automatically on new commits. Configure here.}

Footnotes

1. Please use these labels when submitting a review:
   ❓ #ask: Ask a question.
   💡 #idea: Suggest an idea.
   ⚠️ #issue: Strongly suggest a change.
   🎉 #nice: Share a compliment. ↩