LTS Policy

How Dify Enterprise delivers predictable, secure, long-term supported releases.

What is LTS?

2 features · 2 fixes

LTS (Long-Term Support) versions are maintained exclusively for security, stability, and compliance. No new features are added. Each LTS has a 12-month lifecycle, and two versions are supported simultaneously.

Security

CVE patches, vulnerability scans, and compliance fixes throughout the lifecycle.

Stability

Critical bug fixes only. No feature churn, no breaking changes after release.

Compliance

Regulatory patches backported. Two versions overlap for safe migration windows.

Lifecycle Stages

Stage	Description	Duration
Active Support	Security fixes, critical bug fixes, compliance patches	6 months
Maintenance	Critical/High security fixes only, backported from latest LTS	Until EOL
End of Life	No further support. Must upgrade to a supported LTS.	—

Support Scope

Included

Security vulnerability patches (CVE)

Critical stability / data-loss fixes

Compliance & regulatory fixes

Weekly automated CVE scans

Not Included

New features / enhancements

Performance optimizations

UI / UX improvements

Major dependency upgrades

Vulnerability Fix SLA

Severity	Description	SLA
Critical	Security vulnerability, data loss, service crash	≤ 2 weeks
High	Severe stability issues in production	≤ 2 weeks
Medium	Has workaround available	Case by case
Low	Cosmetic / experience issue	Won't fix

Upgrade & Rollback Policy

Full report →

Supported Upgrade Paths

Only the following paths are officially supported and tested. Skipping major LTS versions is not supported —you must upgrade sequentially.

Path	Type	Notes
v3.8.x → v3.10.x	Cross-LTS	Database migration required. Back up before upgrade.
v3.10.x → v3.12.x	Cross-LTS	Available when v3.12 LTS is released.
v3.10.3 → v3.10.4	Patch	In-place upgrade, no migrations.
v3.8.11 → v3.8.12	Patch	In-place upgrade, no migrations.

Rollback Rules

Only the following paths are officially supported and tested. Skipping major LTS versions is not supported —you must upgrade sequentially.

Scenario	Supported	Method
v3.10.4 → v3.10.3 (same LTS)	YES	helm rollback or specify previous version
v3.8.12 → v3.8.11 (same LTS)	YES	helm rollback or specify previous version
v3.10.x → v3.8.x (cross-LTS)	NO	Database schema changes are irreversible. Restore from backup.