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

HashiCorp Packer

Active
DevOps & CI/CD Latest Version: 1.15.0 Latest Release: Feb 4, 2026

HashiCorp Packer automates the creation of machine images for multiple platforms from a single configuration.

Versions

8

Latest Version

1.15.0

Active Support

3

EOL

5

Lifecycle Timeline

Today
1.15
1.15
1.14
1.14
1.13
1.13
1.12
1.12
1.11
1.11
1.10
1.10
1.9
1.9
1.8
1.8
Active SupportSecurity SupportEOL

Versions

ReleaseRelease DateActive SupportEOLLatest VersionLTSStatus
1.15Feb 4, 2026-No1.15.0No
Active
1.14Jul 30, 2025-No1.14.3No
Active
1.13May 30, 2025-No1.13.1No
Active
1.12Jan 22, 2025-Feb 4, 20261.12.0No
EOL
1.11May 31, 2024-Jul 30, 20251.11.2No
EOL
1.10Dec 5, 2023-May 30, 20251.10.3No
EOL
1.9May 31, 2023-Jan 22, 20251.9.5No
EOL
1.8Mar 4, 2022-May 31, 20241.8.7No
EOL

Frequently Asked Questions

Which versions of HashiCorp Packer have reached end of life?
The following HashiCorp Packer versions have reached end of life and no longer receive security updates: 1.12, 1.11, 1.10, 1.9, 1.8. It is recommended to upgrade to a supported version.
Is it safe to continue using HashiCorp Packer 1.12?
HashiCorp Packer 1.12 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 HashiCorp Packer?
The latest version of HashiCorp Packer is 1.15.0, released in the 1.15 release cycle.
How many versions of HashiCorp Packer are currently supported?
HashiCorp Packer currently has 3 actively supported version(s): 1.15, 1.14, 1.13.
When does HashiCorp Packer 1.15 reach end of life?
HashiCorp Packer 1.15 does not have a specific end-of-life date announced yet.
What should I do when HashiCorp Packer reaches end of life?
When a HashiCorp Packer 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.