You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I searched existing issues and did not find a duplicate.
I am describing a concrete problem or use case, not just a vague idea.
Area
Settings > Providers
Problem or use case
The "Update provider" action always installs @latest. There is no way to target a specific version or roll back. When a CLI update breaks compatibility with T3, manual filesystem changes outside the app are the only option.
Proposed solution
Add version management to the provider settings. Show the currently installed version, allow selecting from recently available versions, and support installing a specific version by number. The package manager commands already support targeting a version. It just isn't exposed.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Before submitting
Area
Settings > Providers
Problem or use case
The "Update provider" action always installs
@latest. There is no way to target a specific version or roll back. When a CLI update breaks compatibility with T3, manual filesystem changes outside the app are the only option.Proposed solution
Add version management to the provider settings. Show the currently installed version, allow selecting from recently available versions, and support installing a specific version by number. The package manager commands already support targeting a version. It just isn't exposed.
All reactions