Feature: Update Rollback #5

Open
opened 2026-08-25 14:30:32 +00:00 by uwayss · 0 comments
Owner

Taking an update back right now means either deleting it or having to push another one to override it. This is mostly fine but unarguably, a rollback mechanism is needed. A rollback should be doable by either sending a rollback update to the runtime that uses the protocol rollback and forces the client to go back to it's embedded bundle or by simply re-publishing a previous update by clicking a button next to it's name (so a "re-deploy")

Taking an update back right now means either deleting it or having to push another one to override it. This is mostly fine but unarguably, a rollback mechanism is needed. A rollback should be doable by either sending a rollback update to the runtime that uses the protocol rollback and forces the client to go back to it's embedded bundle or by simply re-publishing a previous update by clicking a button next to it's name (so a "re-deploy")
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
uwayss/bareed#5
No description provided.