➔ Terragrunt v1.1.1: Dependency Resolution and Safety Fixes
Terragrunt had a busy v1.1.1 window, with 13 commits and 125 files changed around dependency resolution, safer source handling, and clearer crash reports. For teams that run Terragrunt in CI over many units, the headline is simple: fewer false failures around dependency outputs, plus tighter handling for refs, archives, and catalog clones.
➔ Terragrunt v1.0.8 - Faster Read Tracking and S3 Virtual Hosting
Terragrunt v1.0.8 arrived on June 10 2026 with performance improvements for large module sources and better support for S3 virtual hosted style URLs. This release also fixes a long standing issue with assume role list attributes and improves how completed experiments are handled during HCL validation.
➔ Terragrunt v1.0.7: Optional tfr Versions, CAS Beyond Git, and Stack Dependency Cleanup
Terragrunt v1.0.7 shipped on 2026-06-01 with one ergonomic change to tfr:// source URLs, a meaningful expansion of the content addressing experiment, four bug fixes that stop crashes and hangs, and a cleanup pass on the stack-dependencies experiment.
➔ Terragrunt This Week: Dependency Cleanup, CAS Expansion, and Panic Fixes
Terragrunt landed 29 commits this past week. The bulk of the work falls into two buckets: a systematic purge of third party Go dependencies in favor of the standard library, and a significant expansion of the content addressable storage (CAS) layer to support non git sources. Several panic fixes also shipped that affect real user workflows.
➔ Terragrunt v1.0.6 - Bug Fixes and New Experiments
Terragrunt v1.0.6 shipped on May 25, 2026. It is mostly a bug fix wave plus two new experiments and a TUI update for the catalog redesign. The download_dir hang on a non hidden subdirectory and the race in parallel stack parsing are the headline fixes.
➔ Terragrunt v1.0.5 release notes and key changes
Terragrunt v1.0.5 from gruntwork-io shipped on May 18, 2026. The headline change: when the provider cache server talks to the OpenTofu registry, a single terragrunt init now writes a .terraform.lock.hcl with h1: hashes for every platform the registry supports, so you no longer need to run tofu providers lock -platform=... for each target architecture.
➔ Advanced Terragrunt CLI Features - Beyond Basic Infrastructure Management
Discover powerful Terragrunt CLI features that enhance infrastructure management at scale beyond traditional Terraform workflows.