Before submitting
Area
apps/desktop
Problem or use case
I start t3 code each couple of days, and it seems each time I start there is a new version of t3 code AND new providers updates.
Expected: Start t3 code, do work.
Actual: Start t3 code, see update notifications -> FOMO -> update (5 mins), forget why you started t3 code, write this bug report.
Proposed solution
Update providers automatically
Use less aggressive notifications for new versions of t3 code
Why this matters
Less friction.
Smallest useful scope
Auto update providers.
Alternatives considered
No response
Risks or tradeoffs
No response
Examples or references
No response
Contribution
Before submitting
Area
apps/desktop
Problem or use case
I start t3 code each couple of days, and it seems each time I start there is a new version of t3 code AND new providers updates.
Expected: Start t3 code, do work.
Actual: Start t3 code, see update notifications -> FOMO -> update (5 mins), forget why you started t3 code, write this bug report.
Proposed solution
Update providers automatically
Use less aggressive notifications for new versions of t3 code
Why this matters
Less friction.
Smallest useful scope
Auto update providers.
Alternatives considered
No response
Risks or tradeoffs
No response
Examples or references
No response
Contribution