Is your feature request related to a problem? Please describe.
Currently, Typebot only keeps the latest published state of a Typebot. When changes are published, there is no straightforward way to view previous published versions, compare changes, or restore an older version.
This makes production updates risky, especially for self-hosted deployments. If a newly published flow introduces an issue, users must manually recreate the previous flow or rely on external backups.
A similar version-history feature was previously discussed in this issue:
#309
However, it is unclear whether that proposal was implemented or remains part of the roadmap.
Describe the solution you'd like
Add version history support for published Typebots.
Each time a Typebot is published, Typebot should preserve it as a separate published version, for example:
Users should be able to:
- View all previously published versions of a Typebot
- Inspect or compare changes between versions
- Select an older published version
- Republish or roll back to an older version
- Clearly identify which version is currently active
This would allow users to manage production Typebots more safely and make rollbacks predictable.
A pull request implementing version support has already been created:
#2563
Describe alternatives you've considered
The current alternatives are:
- Manually duplicating a Typebot before publishing changes
- Exporting and storing Typebot configurations externally
- Using database backups or snapshots
- Manually recreating an older flow after a problematic deployment
These approaches require additional maintenance and do not provide a native, reliable, or user-friendly versioning workflow.
Is your feature request related to a problem? Please describe.
Currently, Typebot only keeps the latest published state of a Typebot. When changes are published, there is no straightforward way to view previous published versions, compare changes, or restore an older version.
This makes production updates risky, especially for self-hosted deployments. If a newly published flow introduces an issue, users must manually recreate the previous flow or rely on external backups.
A similar version-history feature was previously discussed in this issue:
#309
However, it is unclear whether that proposal was implemented or remains part of the roadmap.
Describe the solution you'd like
Add version history support for published Typebots.
Each time a Typebot is published, Typebot should preserve it as a separate published version, for example:
Users should be able to:
This would allow users to manage production Typebots more safely and make rollbacks predictable.
A pull request implementing version support has already been created:
#2563
Describe alternatives you've considered
The current alternatives are:
These approaches require additional maintenance and do not provide a native, reliable, or user-friendly versioning workflow.