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

Vinyl Cache

Active
Other Latest Version: 9.0.1 Latest Release: May 18, 2026

Versions

11

Latest Version

9.0.1

Active Support

3

EOL

8

Lifecycle Timeline

Today
9.0
9.0
8.0
8.0
7.7
7.7
7.6
7.6
7.5
7.5
7.4
7.4
7.3
7.3
7.2
7.2
7.1
7.1
7.0
7.0
Active SupportSecurity SupportEOL

Versions

ReleaseRelease DateActive SupportEOLLatest VersionLTSStatus
9.0Mar 16, 2026YesMar 16, 20279.0.1No
Active
8.0Sep 15, 2025YesSep 15, 20268.0.2No
Active
7.7Mar 17, 2025NoMar 15, 20267.7.3No
EOL
7.6Sep 13, 2024NoSep 15, 20257.6.5No
EOL
7.5Mar 18, 2024NoMar 15, 20257.5.0No
EOL
7.4Sep 15, 2023NoSep 15, 20247.4.3No
EOL
7.3Mar 15, 2023NoMar 15, 20247.3.2No
EOL
7.2Sep 15, 2022NoSep 15, 20237.2.1No
EOL
7.1Mar 15, 2022NoMar 15, 20237.1.2No
EOL
7.0Sep 15, 2021NoSep 15, 20227.0.3No
EOL
6.0Mar 15, 2018YesNo6.0.18
Yes
Active

Frequently Asked Questions

Which versions of Vinyl Cache have reached end of life?
The following Vinyl Cache versions have reached end of life and no longer receive security updates: 7.7, 7.6, 7.5, 7.4, 7.3, 7.2, 7.1, 7.0. It is recommended to upgrade to a supported version.
Is it safe to continue using Vinyl Cache 7.7?
Vinyl Cache 7.7 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 Vinyl Cache?
The latest version of Vinyl Cache is 9.0.1, released in the 9.0 release cycle.
How many versions of Vinyl Cache are currently supported?
Vinyl Cache currently has 3 actively supported version(s): 9.0, 8.0, 6.0.
When does Vinyl Cache 9.0 reach end of life?
Vinyl Cache 9.0 is scheduled to reach end of life on Mar 16, 2027.
What should I do when Vinyl Cache reaches end of life?
When a Vinyl Cache 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.