Release Management
Liberate provides release management capabilities that enable teams to version workflows, create release artifacts, and deploy to QA or Production environments with confidence.Overview
Release management in Liberate follows a simple flow:Revisions
Revisions are automatic snapshots of your workflow saved whenever you make changes.How Revisions Work
- Auto-saved: Liberate automatically saves a revision whenever there’s a difference in the workflow
- Tracked history: Every change is recorded, allowing you to see the full evolution of your workflow
- Recoverable: You can view, compare, or restore any previous revision
Viewing Revision History
- Open your workflow in the canvas
- Click Version History at the top of the canvas
- Browse the list of all saved revisions
- Timestamp of when it was saved
- Who made the change (if applicable)
- Summary of modifications
Releases
Releases are tagged versions of your workflow that are ready for deployment. Unlike revisions (which are automatic), releases are intentionally created when you’re ready to deploy.Creating a Release
From the current version:- Click the top menu in the workflow canvas
- Select Create Release
- Add release notes describing the changes
- Click Create
- Open Version History
- Find the revision you want to release
- Click on the revision and select Create Release
- Add release notes
- Click Create
Release Notes
Always include release notes with your releases. Good release notes should describe:- What changed (new features, bug fixes, improvements)
- Why it changed (business requirement, bug report, optimization)
- Any dependencies or considerations for deployment
Deploying Releases
The Release Tab on the right panel of the workflow interface manages deployments.Deployment Targets
How to Deploy
- Open the Release Tab in the right panel
- Select the release you want to deploy
- Choose the target environment (QA or Production)
- Confirm the deployment
- Monitor for any errors or issues
Deployment Checklist
Before deploying to Production, verify:- Workflow tested in Preview mode with sample data
- Release deployed and validated in QA environment
- Connections configured for Production (different credentials than QA)
- Stakeholders notified of upcoming changes
- Rollback plan in place if issues occur
Rollback
If a deployment causes issues, you can quickly rollback to a previous stable release.When to Rollback
- API errors after deployment
- Unexpected workflow behavior
- Data transformation issues
- Integration failures
How to Rollback
- Open the Release Tab in the right panel
- Find the previous known-good release
- Select Deploy for that release
- Choose the environment to rollback (QA or Production)
- Confirm the rollback
Rollback Best Practices
- Document issues: Note what went wrong before rolling back
- Communicate: Inform stakeholders about the rollback
- Investigate: After rolling back, debug the issue in Preview before re-deploying
- Test thoroughly: Ensure the fix works in QA before attempting Production again
Best Practices
Versioning Strategy
Use semantic versioning for releases:Release Workflow
Environment Parity
Keep QA and Production as similar as possible:- Same workflow logic
- Same connection configurations (different credentials)
- Same retry strategies and error handling
Next Steps
Preview Mode
Test workflows before creating releases
Connections
Configure environment-specific credentials
Error Handling
Build robust error handling into workflows
Workflow Quickstart
Learn the basics of building workflows

