EOL.Wiki EOL.Wiki
← ← Back to all products

Apache DolphinScheduler

Active
Middleware Latest Version: 3.4.2 Latest Release: May 30, 2026

Apache DolphinScheduler is a distributed and extensible visual workflow scheduling system for big data, supporting DAG-based orchestration of data pipeline tasks.

Versions

7

Latest Version

3.4.2

Active Support

2

EOL

5

Lifecycle Timeline

Today
3.4
3.4
3.3
3.3
3.2
3.2
3.1
3.1
3.0
3.0
2.0
2.0
1.3
1.3
Active SupportSecurity SupportEOL

Versions

ReleaseRelease DateActive SupportEOLLatest VersionLTSStatus
3.4Jan 20, 2026YesNo3.4.2No
Active
3.3Aug 25, 2025YesNo3.3.2No
Active
3.2Oct 11, 2023NoYes3.2.2No
EOL
3.1Sep 28, 2022NoYes3.1.9No
EOL
3.0Aug 5, 2022NoYes3.0.6No
EOL
2.0Dec 13, 2021NoYes2.0.9No
EOL
1.3Jul 13, 2020NoYes1.3.9No
EOL

Frequently Asked Questions

Which versions of Apache DolphinScheduler have reached end of life?
The following Apache DolphinScheduler versions have reached end of life and no longer receive security updates: 3.2, 3.1, 3.0, 2.0, 1.3. It is recommended to upgrade to a supported version.
Is it safe to continue using Apache DolphinScheduler 3.2?
Apache DolphinScheduler 3.2 has reached end of life and no longer receives security patches or bug fixes. Continuing to use it may expose your systems to known vulnerabilities. We strongly recommend upgrading to a supported version.
What is the latest version of Apache DolphinScheduler?
The latest version of Apache DolphinScheduler is 3.4.2, released in the 3.4 release cycle.
How many versions of Apache DolphinScheduler are currently supported?
Apache DolphinScheduler currently has 2 actively supported version(s): 3.4, 3.3.
When does Apache DolphinScheduler 3.4 reach end of life?
Apache DolphinScheduler 3.4 does not have a specific end-of-life date announced yet.
What should I do when Apache DolphinScheduler reaches end of life?
When a Apache DolphinScheduler version reaches end of life, you should: 1) Plan your migration to a supported version as soon as possible. 2) Review the release notes for breaking changes. 3) Test your applications thoroughly in a staging environment. 4) Update your dependencies to ensure compatibility with the new version.