The first release candidate for Terragrunt 1.0 is here! After years of refinement, Terragrunt is ready for its 1.0 milestone, and we need your help to get it across the finish line.
We anticipate 2-3 release candidates before Terragrunt 1.0 ships, which means you have roughly 6-8 weeks to influence the final release. If there's something about Terragrunt's current behavior that you'd want changed, now is the time to speak up.
Try It Now
Get started with RC1:
(or use your preferred installation method documented in the Terragrunt installation docs)
We recommend testing in a lower environment first. Here are some things to try:
- Try out the new CLI experience with the new CLI syntax and compare the experience
- Test the new filter flag by replacing your existing
-terragrunt-include-dir/-queue-include-dirusage - Try Stacks with a set of related units you currently deploy together
Your Feedback Shapes 1.0
Your feedback directly influences what ships in Terragrunt 1.0. We're especially interested in:
- The new CLI structure and migration experience
- Stacks behavior in real-world configurations
- Any edge cases or regressions in your workflows
Let us know how it goes:
- No issues? Drop a positive emoji on the GitHub release.
- Found a bug or have feedback? Share it in the dedicated GitHub Discussion or the #feedback channel in Discord.
Until 1.0 ships, Terragrunt maintainers are focused entirely on community feedback, bug fixes, and documentation. No new features are planned.
What's in 1.0
The road to 1.0 has brought significant improvements to Terragrunt:
- CLI Redesign: A streamlined command structure with a new Filter Flag that replaces seven existing flags with a sophisticated query syntax.
- Terragrunt Stacks: A new IaC abstraction layer for managing related infrastructure as a single deployable stack.
- Runner Pool: A new concurrency model that significantly improves throughput and error handling.
- Overhauled Logging: Better visibility into what Terragrunt is doing and why.
- Run Reports: Programmatic output for assessing Terragrunt execution results.
For a complete overview, see The Road to 1.0: Release Schedule.
Our Stability Promise
The term "breaking change" means something different to different people, and every change can, in some way, be a breaking change to someone.

On the road to 1.0, we at Gruntwork have done some serious thinking about compatibility guarantees. We want you to be confident that Terragrunt 1.x releases won't break your important workflows.
To that end, we've explicitly documented Terragrunt 1.0 Guarantees so you understand what we consider a breaking change and what you can rely on. This is a living document, but we won't remove guarantees. Updates will only clarify ambiguity.
TL;DR: What's stable, what's not
- Stable in 1.x: CLI flags, serialized output from
findand Run Reports, and all HCL configurations. Yourterragrunt.hcl,terragrunt.stack.hcl, and included.hclfiles won't need edits for any 1.x release. - May change: Experimental functionality remains unstable until (and if) it becomes generally available. Human-readable output from commands like list and catalog may change to improve usability. Try to avoid parsing these programmatically.
For Gruntwork Customers
Terragrunt Pipelines
The changes on the road to 1.0 were made with careful consideration for Terragrunt Pipelines customers. As long as you are using v4+ of Pipelines, you will experience no breaking changes from Terragrunt by the time Terragrunt 1.0 is released, or in any 1.x release.
The Minimum Supported Version of Terragrunt may be raised across major Pipelines releases to ensure customers can take advantage of new capabilities in Terragrunt 1.x minor releases (see the compatibility matrix for details).
Terragrunt Enterprise Support
If you currently use Terragrunt at a large enterprise and want help making the transition to Terragrunt 1.0, please reach out to our sales team for Terragrunt Enterprise Support.
If you currently have Terragrunt Enterprise Support, we will work with you to ensure you are supported through this transition.
Whether your experience with RC1 is smooth or bumpy, we want to hear about it. Thank you for helping us make Terragrunt the best way to manage infrastructure at scale.



- No-nonsense DevOps insights
- Expert guidance
- Latest trends on IaC, automation, and DevOps
- Real-world best practices



