Guidance on Updates Approach

[bozobit]

Is your feature request related to a problem? Please describe.
As I'm learning and experimenting with next-forge, setting up the configuration with Vercel and starting to add functionality. I'm not clear what my strategy should be with respect to updates (https://docs.next-forge.com/updates). When I attempt an upgrade of next-forge from one version to the next, even on an unchanged template, I seem always to get new errors I don't understand and struggle to clear them. When I run bump-deps, I also get errors introduced on build. (Also, how is that related to dependabot?) The whole thing feels quite fragile and the new releases are coming nearly daily. In just a few weeks, I went from 3.1.8 to 3.2.16 and I'm struggling to keep up or know whether I should even try to keep current. I really don't know how I should be managing this or thinking properly about it. I feel like I'm running the risk of spending all my time managing configurations and updates rather than building the product.

Describe the solution you'd like
Some kind of guidance in the documentation on what a sensible upgrade strategy should be and how I should go about it. Or perhaps a Discord forum where we can help each other. Or perhaps some system of setting "stable" releases that we can count on for a defined period (at least a few months) would help.

Describe alternatives you've considered
Struggling to come up with one other than just taking the version I started with and accepting the risk of it becoming obsolete.