How to handle the frequency of new TUnit releases?

[alastairlundy]

Hi,
I switched to TUnit for a few of my projects a few weeks back, starred the repo, and since then I've noticed new versions of TUnit being released, more or less, on a daily basis. Don't get me wrong I appreciate the fast paced nature of development on TUnit and TUnit has been a breath of fresh air vs XUnit but, I'm not sure how to proceed with new versions e,g, update weekly, or update when practical. Dependabot looks for updates in some of my GitHub repos daily (I'd rather not wait a week to update dependencies) and finds new TUnit versions daily, thus the dilemma of how often to update the TUnit version in a project.

How often should a project relying on TUnit be updating its TUnit version?
Thanks

[thomhurst]

There shouldn't be any breaking changes (hopefully!) so there is no rush to update if you don't need to.

If you haven't had any issues or bugs, and don't need any of the new features in releases, then hold off.

Ultimately just check the release notes and see if anything in there is nice or fixes any issues you may have experienced.