chore(deps): update

[dargmuesli]

🔗 Linked issue

n/a

❓ Type of change

• [ ] 📖 Documentation (updates to the documentation or readme)
• [ ] 🐞 Bug fix (a non-breaking change that fixes an issue)
• [ ] 👌 Enhancement (improving an existing functionality)
• [ ] ✨ New feature (a non-breaking change that adds functionality)
• [x] 🧹 Chore (updates to the build process or auxiliary tools and libraries)
• [ ] ⚠️ Breaking change (fix or feature that would cause existing functionality to change)

📚 Description

Just some updates. Currently, renovate does not run that often, I think, so many update branches accumulate over time. They are all retried once one of those is merged, which is kind of inefficient, I think. What do you think about grouping all non-major updates into one PR, @danielroe?

[codecov[bot]]

Codecov Report

All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 25.07%. Comparing base (dc164cc) to head (f7aeda6). Report is 75 commits behind head on main.

Additional details and impacted files

```diff @@ Coverage Diff @@ ## main #330 +/- ## ========================================== + Coverage 19.26% 25.07% +5.80% ========================================== Files 12 11 -1 Lines 493 323 -170 Branches 23 22 -1 ========================================== - Hits 95 81 -14 + Misses 398 242 -156 ```

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

[danielroe]

That makes sense!

[dargmuesli-bot]

:tada: This PR is included in version 0.9.5 :tada:

The release is available on:

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

Your semantic-release bot :package::rocket: