Nomad End of Life (EOL) Dates and End of Support (EOS) Dates
Nomad end of life (EOL) and end of support (EOS) dates: 12 Nomad versions have reached EOL, including Nomad 1.11 (EOL date: Oct 31, 2026) — no longer receiving security updates or patches. Nomad 2.1.1 is the current supported release — 3 versions in active support. Also see Hashicorp Boundary end of support life for related end-of-life information.
Currently Supported Nomad Releases - Active EOS/EOSL Support (3)
Nomad End of Life (EOL) Releases - No Longer Supported (12)
| Release | Released | Security Support | Latest | LTS |
|---|---|---|---|---|
| 1.11 | (1 year ago) | (3 weeks and 1 day ago) | 1.11.3 (8 months ago) | - |
| 1.9 | (2 years and 1 month ago) | (7 months ago) | 1.9.7 (1 year and 8 months ago) | - |
| 1.8 (LTS) | (2 years and 5 months ago) | (6 months ago) | 1.8.4 (2 years and 2 months ago) | LTS |
| 1.7 | (2 years and 11 months ago) | (1 year and 7 months ago) | 1.7.7 (2 years and 7 months ago) | - |
| 1.6 | (3 years and 4 months ago) | (2 years and 1 month ago) | 1.6.10 (2 years and 7 months ago) | - |
| 1.5 | (3 years and 8 months ago) | (2 years and 5 months ago) | 1.5.17 (2 years and 7 months ago) | - |
| 1.4 | (4 years and 1 month ago) | (2 years and 11 months ago) | 1.4.14 (3 years ago) | - |
| 1.3 | (4 years and 6 months ago) | (3 years and 4 months ago) | 1.3.16 (3 years and 3 months ago) | - |
| 1.2 | (5 years ago) | (3 years and 8 months ago) | 1.2.16 (3 years and 9 months ago) | - |
| 1.1 | (5 years and 6 months ago) | (4 years and 1 month ago) | 1.1.18 (4 years and 2 months ago) | - |
| 1.0 | (5 years and 11 months ago) | (4 years and 6 months ago) | 1.0.18 (4 years and 9 months ago) | - |
| 0.12 | (6 years and 4 months ago) | (5 years ago) | 0.12.12 (5 years and 6 months ago) | - |
Nomad end of life is the date after which HashiCorp stops shipping fixes for a release. This workload orchestrator, which runs containers, batch jobs and plain binaries, follows a fixed schedule, and on 27 October 2026 only Nomad 2.0, 1.11 and 1.10 are still maintained, with 1.11 closing on 31 October 2026.
HashiCorp Nomad End of Life Dates by Release Date
The table lists every supported release plus the lines that just retired, using the security dates published on endoflife.date. An EOL date is a deadline for patches, not a ban on running the software.
| Release | Release date | Security support ends | Latest patch |
|---|---|---|---|
| 2.0 | 21 April 2026 | 30 April 2028 | 2.0.7 |
| 1.11 | 11 November 2025 | 31 October 2026 | 1.11.3 |
| 1.10 (LTS) | 9 April 2025 | 30 April 2027 | 1.10.5 |
| 1.9 | 10 October 2024 | 21 April 2026 | 1.9.7 |
| 1.8 (LTS) | 28 May 2024 | 30 April 2026 | 1.8.4 |
Which Nomad Versions Are Still Supported
Today, Nomad versions 2.0, 1.11 and 1.10 receive security fixes. Versio.io counts 335 builds across 27 releases, and 86 of them are unstable versions. Its feed still lists 1.9 as supported, so trust the vendor dates over any tracker, and check the GitHub release page for the exact tag you run.
Latest Version and Latest Patch Version
The latest version is 2.0.7, shipped on 17 September 2026, which is also the latest patch version of the 2.0 line. A 2.1.0 release candidate appeared on 20 October.
Nomad Releases and Version History
Nomad releases began with 0.1 in September 2015, reached 1.0 in December 2020 and 2.0 in April 2026. The version history on GitHub gives each tag its own notes with bug fixes, features and deprecations, and HashiCorp posts release updates for every product. The newest pre-release adds an experimental batch job queue, and the Nomad documentation explains each setting.
Security Support and Breaking Changes
Once a line passes its end date, moving up is the only route to fixes, so read the breaking changes first. For anyone leaving 1.11 or 1.10, the 2.1.0-rc.1 notes require agent:write permission to join servers and remove the old retry_join blocks. Review each changelog before moving.
Nomad Facts: Licence, CVEs and Version Command
Nomad uses the Business Source License, a licence that does not change the support dates. The same dates apply whether you deploy a microservice or a scheduled job across clusters, on-prem or in the cloud, and to its native Consul and Vault integrations. Versio.io reports that 233 versions are affected by CVE entries. Run the version command, nomad version, to see which build you have.
Nomad Support Period and Release Strategy
HashiCorp supports generally available releases of active products for up to two years. Code-fixes and hot-fixes arrive as a new minor release on top of the latest major release branch, for up to two releases from the current one. A major release is any change to the first or second digit of X.Y.Z, while a bump to Z is a minor release.
The vendor expects customers to stay current within two releases of the newest one. That release cadence, along with the versioning rule, is why a version can be only months old and still near its end.
Plan Upgrades Before Support Ends
- Confirm your build with
nomad versionand match it to the table above: 1.11 closes on 31 October 2026. - On 1.10 LTS, you have until 30 April 2027, but test the next line on a staging cluster now.
- Treat the move to 2.0 as a migration, with a rollback plan.
- Schedule the work at least a quarter before your line's end date.
Long-Term Support: LTS and Nomad Enterprise EOL
HashiCorp offered long-term support for certain commercial products released before April 2026. LTS stretched the support window to two years, with critical fixes, security patches and hardened upgrade paths that let you skip intermediate major releases in one upgrade path.
Nomad Enterprise 1.10.x is the last LTS version, and the end of LTS arrives in April 2027. The siblings follow a similar support model: Consul Enterprise 1.21 and Vault Enterprise 1.19 also end in April 2027, Terraform Enterprise 1.2 in November 2027 and Boundary Enterprise 0.21 in December 2027.
IBM Support Lifecycle and Support Cycle 2 for Nomad
Since April 2026, all HashiCorp self-managed products are moving to IBM's Support Cycle-2 (SC2, also written SC-2). IBM lists IBM Nomad Self-Managed under product 5900-BNK, next to IBM Consul Self-Managed and IBM Vault Self-Managed, and ends mod/fix support for 1.8.x on 30 April 2026, 1.11.x on 31 October 2026 and 1.10.x on 30 April 2027.
Support Policy for Releases Since March 2025
Builds released between March 2025 and April 2026 follow the support lifecycle addendum, while anything older keeps the original policy. The support details and any support transition come with 12 months' notice, and Terraform and Boundary have their own dates.