-
-
Notifications
You must be signed in to change notification settings - Fork 469
Add an autoupdater for cloud mode #1046
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
deep1401
commented
Dec 11, 2025
Codecov Report❌ Patch coverage is
📢 Thoughts on this report? Let us know! |
deep1401
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Maybe we talk more on this and merge post-release?
Yeah I think let's play around and revisit this after the release. |
|
I was thinking, do we even want an auto-updater in cloud mode? Generally with cloud apps developers want some control over which users are seeing which version of the app. When we do updates in cloud, they're generally rolling updates so we can roll out the new version to a certain % of the users, and roll back if we detect any errors early on. It might be hard to detect/troubleshoot issues in the code if we can't guarantee that a user is on a particular version of the app. Or maybe I'm misunderstanding the intention/terminology here, are we planning on having our API running in the cloud, or will it always be a local thing? |
|
I'm worried that if an admin sets up Transformer lab on their team, then users shouldn't be able to update the code (they may have added custom code, or are tied to a specific version). Autoupdate only makes sense if it is a single user. So maybe we can just make the "update available" really loud instead of autoupdate. |