Skip to content

Update dependency gruntwork-io/terragrunt to v0.83.0 #390

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Update dependency gruntwork-io/terragrunt to v0.83.0 #390

wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jan 16, 2025 •
edited
Loading

This PR contains the following updates:

Package Update Change
gruntwork-io/terragrunt minor 0.78.4 -> 0.83.0

Release Notes

gruntwork-io/terragrunt (gruntwork-io/terragrunt)

v0.83.0

Compare Source

✨ New Features

  • Added initial implementation of runner-pool to improve unit apply performance. The feature can be enabled using the --experiment runner-pool flag.

RFC: https://github.com/gruntwork-io/terragrunt/issues/3629

🛠️ Breaking Changes

  • Updated log messages to use "Unit" terminology instead of "Module" for improved clarity and consistency.

🐛 Bug Fixes

  • Fixed flaky tests related to the provider cache.
  • Added explicit check for user-defined --tf-path flag.
  • Updated Dockerfile to support Starlight documentation generation.
  • Fixed incorrect lock file constraints generated by the Terragrunt Provider Cache.
  • Fixed discovery of Terragrunt files in runner-pool, ensuring correct file resolution during execution.

What's Changed

New Contributors

Full Changelog: gruntwork-io/terragrunt@v0.82.4...v0.83.0

v0.82.4

Compare Source

✨ New Features

Support for OpenTofu 1.10 Native S3 Locking

The remote_state S3 backend now integrates natively with the OpenTofu 1.10 feature of state locking via S3 without the usage of DynamoDB using the new use_lockfile attribute.

### Configure OpenTofu/Terraform state to be stored in S3 with native S3 locking instead of DynamoDB.
### This uses S3 object conditional writes for state locking, which requires OpenTofu >= 1.10.
remote_state {
  backend = "s3"
  config = {
    bucket       = "my-tofu-state"
    key          = "${path_relative_to_include()}/tofu.tfstate"
    region       = "us-east-1"
    encrypt      = true
    use_lockfile = true
  }
}

In previous releases, if users wanted to integrate with this OpenTofu feature, they would have to use the generate attribute, which opts users out of more advanced features of Terragrunt remote state management like automatic provisioning of state resources.

By using the native attribute in config, users can retain the benefits of automatic backend bootstrapping in addition to native integration with the new OpenTofu feature.

You can learn more about backend configurations in the HCL docs.

What's Changed

Full Changelog: gruntwork-io/terragrunt@v0.82.3...v0.82.4

v0.82.3

Compare Source

🧪 Experiments Added

Introduction of the auto-provider-cache-dir experiment

The new auto-provider-cache-dir experiment has been added to automatically configure OpenTofu provider caching when certain conditions are met:

  • You are using OpenTofu
  • You are using a version of OpenTofu >= 1.10

This leverages recent improvements in how OpenTofu handles provider caching to allow for safe concurrent access to provider plugins in OpenTofu 1.10.

In micro-benchmarks, the native provider cache directory out-performs the Provider Cache Server, as the overhead of starting and running the provider cache server is eliminated.

Screenshot 2025-06-25 at 12 38 05 PM

Once generally available, this feature will be enabled by default, automatically providing performance improvements to Terragrunt users using OpenTofu >= 1.10. If you are currently using the Provider Cache Server, you are advised to experiment with this feature, and share your feedback.

You can learn more about the feature in the dedicated feature docs, including a comparison with the Provider Cache Server, so you can learn if limitations in how the native OpenTofu provider cache directory will result in a requirement to continue using the Provider Cache Server going forward.

Special thanks to @​cam72cam for coordinating with us to get this long-awaited feature supported in OpenTofu to meet the needs of the IaC community.

✨ New Features

--version-manager-file-name Flag Added

During a run --all, Terragrunt memoizes the version of OpenTofu/Terraform being run to determine if version constraints are being satisfied, without doing unnecessary work to repeatedly check the version of OpenTofu/Terraform being run in each directory.

To ensure that users using tool managers are able to leverage different versions of OpenTofu/Terraform in different directories, the cache key for this memoization includes calculations based on common version manager tools.

By default, the following are detected:

  • .terraform-version
  • .tool-versions
  • .mise.toml
  • mise.toml

To support the usage of any arbitrary tool manager, a new --version-manager-file-name flag has been introduced to allow configurability over this list.

To learn more about --version-manager-file-name read the docs.

What's Changed

Full Changelog: gruntwork-io/terragrunt@v0.82.2...v0.82.3

v0.82.2

Compare Source

🐛 Bug Fixes

get_terragrunt_dir returns appropriate directory

The get_terragrunt_dir() HCL function now returns the expected stack directory containing a terragrunt.stack.hcl when used in a terragrunt.stack.hcl file.

### terragrunt.stack.hcl

unit "unit_a" {
  source = "../../unit_a"
  path   = "unit_a"
  values = {
    terragrunt_dir = get_terragrunt_dir()
  }
}
non-git default templates supported for Catalog/Scaffold

A bug in how the default_template attribute of the catalog configuration block worked resulted in a requirement that the default template be a Git repository. That bug has been resolved, removing the restriction.

catalog {
  urls             = ["../local-catalog"]
  default_template = "../not-a-git-repo"
}

What's Changed

Full Changelog: gruntwork-io/terragrunt@v0.82.1...v0.82.2

v0.82.1

Compare Source

🧪 Experiments Updated

The cas experiment now supports terraform block source attributes

The cas experiment now supports de-duplication of OpenTofu/Terraform module source cloning during unit initialization.

This both reduces time spent cloning OpenTofu/Terraform module sources by reducing network bandwidth overhead, and reduces disk utilization.

Screenshot 2025-06-26 at 7 01 38 AM

You can learn more about the CAS feature in the dedicated feature documentation.

🐛 Bugs Fixed

The hcl validate command now returns an appropriate exit code

When using hcl validate, if any unit fails validation when run against a stack of units, the final exit code will be non-zero when any unit fails validation.

While this is technically a bugfix that is a 🛠️ breaking change in behavior, maintainers have opted to release this as part of a patch release, as it's what most users expect from the command and it's how the command is documented. We are also trying to reduce the number of minor releases on the road to 1.0 to make it easier to focus on the big changes that require significant adjustment in usage of Terragrunt, and want to make sure that users take special note of breaking removal of deprecated functionality.

Avoiding the breaking change is fairly simple:

terragrunt hcl validate || true

What's Changed

Full Changelog: gruntwork-io/terragrunt@v0.82.0...v0.82.1

v0.82.0

Compare Source

Description

OpenTofu 1.10 support: We are now testing Terragrunt against OpenTofu 1.10, and is confirmed to be working.

NOTE: Although this release is marked as backward incompatible, it is functionally compatible as nothing has been changed in Terragrunt internals. The minor version release is useful to mark the change in the OpenTofu version that is being tested.

What's Changed

Full Changelog: gruntwork-io/terragrunt@v0.81.10...v0.82.0

v0.81.10

Compare Source

What's Changed

Full Changelog: gruntwork-io/terragrunt@v0.81.9...v0.81.10

v0.81.9

Compare Source

🧪 Experiments Updated

Styling for Run Summary Updated

Per design feedback, the styling for Run Summaries has been updated slightly.

summary-styling

The report is now considered feature complete. Any further updates will be made to address community feedback.

What's Changed

Full Changelog: gruntwork-io/terragrunt@v0.81.8...v0.81.9

v0.81.8

Compare Source

✨ New Features

Scaffold now supports Boilerplate dependencies and partials

The Scaffold feature now supports leveraging Boilerplate dependencies and partials.

This was a missing feature in the integration between Scaffold and Boilerplate, and Terragrunt users do not have to change anything in how they invoke Scaffold to have custom Boilerplate templates properly render using those Boilerplate features.

Special thanks to @​tgeijg for contributing this feature!

What's Changed

Full Changelog: gruntwork-io/terragrunt@v0.81.7...v0.81.8

v0.81.7

Compare Source

🧪 Experiments Updated

--summary-unit-duration replaced with --summary-per-unit

Per design feedback, the flag --summary-unit-duration has been replaced with --summary-per-unit in the report experiment.

The final summary at the end of runs was updated from looking like this by default:

$ terragrunt run --all plan

### Omitted for brevity...

❯❯ Run Summary
   Duration:   62ms
   Units:      3
   Succeeded:  3

To looking like this:

$ terragrunt run --all plan

### Omitted for brevity...

❯❯ Run Summary  3 units  62ms
   ────────────────────────────
   Succeeded    3

In addition, the flag --summary-unit-duration that resulted in summaries that looked like this:

$ terragrunt run --all plan --summary-unit-duration

### Omitted for brevity...

❯❯ Run Summary
   Duration:   10m
      long-running-unit:    10m
      medium-running-unit:  12s
      short-running-unit:   5ms
   Units:      3
   Succeeded:  3

Was replaced with the --summary-per-unit flag that results in summaries that look like this:

$ terragrunt run --all plan --summary-per-unit

### Omitted for brevity...

❯❯ Run Summary  3 units     10m
   ──────────────────────────────
   Succeeded (3)
      long-running-unit     10m
      medium-running-unit   12s
      short-running-unit    5ms

This was done to streamline the information conveyed by the run summary, and to maximize leverage over the screen real estate taken by the summary.

The report experiment is still ongoing, and community feedback is encouraged. Please share any feedback you may have before the design of Run Reports and Run Summaries are finalized.

What's Changed

Full Changelog: gruntwork-io/terragrunt@v0.81.6...v0.81.7

v0.81.6

Compare Source

🐛 Bug Fixes

The catalog command no longer panics during scaffolding

A mistake in a refactor of internal logging caused a panic during scaffolding while using the Terragrunt Catalog Terminal User Interface (TUI).

That bug has been fixed.

IaC Engines now properly handle errors during init and shutdown

Some missing error handling in IaC Engines has been introduced to properly handle failed initialization and shutdown by IaC Engines.

What's Changed

Full Changelog: gruntwork-io/terragrunt@v0.81.5...v0.81.6

v0.81.5

Compare Source

✨ New Features

Terragrunt now supports using credentials in .terraformrc files

Terragrunt now supports credentials stored in .terraformrc files when fetching from private registries, in addition to the fallback mechanism of using TG_TF_REGISTRY_TOKEN.

Special thanks to @​dlundgren for contributing this feature!

What's Changed

New Contributors

Full Changelog: gruntwork-io/terragrunt@v0.81.4...v0.81.5

v0.81.4

Compare Source

🧪 Experiments Updated

The reports experiment now supports the --summary-unit-duration flag

As part of delivering #​3628 , the reports experiment has been updated to support optionally displaying unit-level duration information in the Run Summary.

You can now optionally display the duration for each unit run as part of the Run Summary by adding the --summary-unit-duration flag to your run commands:

e.g.

$ terragrunt run --all plan --summary-unit-duration

### Omitted for brevity...

❯❯ Run Summary
   Duration:   10m
      long-running-unit:    10m
      medium-running-unit:  12s
      short-running-unit:   5ms
   Units:      3
   Succeeded:  3

By default, this information will be omitted.

For more information, see Showing unit durations in the docs.

What's Changed

Full Changelog: gruntwork-io/terragrunt@v0.81.3...v0.81.4

v0.81.3

Compare Source

🧪 Experiments Updated

The reports experiment now supports generating reports in JSON format

As part of delivering #​3628 , the reports experiment has been updated to support JSON report generation in addition to the default of CSV report generation.

To generate a report using JSON formatting, either use the --report-format flag to explicitly set the format to one of csv or json or provide a --report-file with a .csv or .json file extension to implicitly select the report format.

The JSON version of report summaries look like this:

[
  {
    "name": "second-exclude",
    "started": "2025-06-09T12:50:02.59688-04:00",
    "ended": "2025-06-09T12:50:02.596881-04:00",
    "result": "excluded",
    "reason": "exclude block"
  },
  {
    "name": "first-exclude",
    "started": "2025-06-09T12:50:02.596882-04:00",
    "ended": "2025-06-09T12:50:02.596882-04:00",
    "result": "excluded",
    "reason": "exclude block"
  },
  {
    "name": "error-ignore",
    "started": "2025-06-09T12:50:02.597139-04:00",
    "ended": "2025-06-09T12:50:02.742775-04:00",
    "result": "succeeded"
  }
]

For more information, read the documentation on the Run Report.

The reports experiment now supports generating a JSON schema for reports

As part of delivering #​3628 , the reports experiment has been updated to support generating a JSON schema following the JSON Schema specification in addition to generating reports.

To generate a schema, use the --report-schema-file flag.

The schema looks like this:

{
  "items": {
    "$schema": "https://json-schema.org/draft/2020-12/schema",
    "$id": "https://terragrunt.gruntwork.io/schemas/run/report/v1/schema.json",
    "properties": {
      "Started": {
        "type": "string",
        "format": "date-time"
      },
      "Ended": {
        "type": "string",
        "format": "date-time"
      },
      "Reason": {
        "type": "string",
        "enum": [
          "retry succeeded",
          "error ignored",
          "run error",
          "--queue-exclude-dir",
          "exclude block",
          "ancestor error"
        ]
      },
      "Cause": {
        "type": "string"
      },
      "Name": {
        "type": "string"
      },
      "Result": {
        "type": "string",
        "enum": [
          "succeeded",
          "failed",
          "early exit",
          "excluded"
        ]
      }
    },
    "additionalProperties": false,
    "type": "object",
    "required": [
      "Started",
      "Ended",
      "Name",
      "Result"
    ],
    "title": "Terragrunt Run Report Schema",
    "description": "Schema for Terragrunt run report"
  },
  "type": "array",
  "title": "Terragrunt Run Report Schema",
  "description": "Array of Terragrunt runs"
}

For more information, read the documentation on the Run Report.

What's Changed

Full Changelog: gruntwork-io/terragrunt@v0.81.2...v0.81.3

v0.81.2

Compare Source

🧪 Experiments Updated

The reports experiment now supports generating reports

As part of delivering #​3628 , the reports experiment has been updated to support CSV report generation.

When the reports experiment is enabled, and the --report-file argument is passed to a run --all / run --graph / stack run command, Terragrunt will generate a CSV report of the run in addition to the summary that is emitted by default.

The report summary looks like this:

Name,Started,Ended,Result,Reason,Cause
first-exclude,2025-06-05T16:28:41-04:00,2025-06-05T16:28:41-04:00,excluded,exclude block,
second-exclude,2025-06-05T16:28:41-04:00,2025-06-05T16:28:41-04:00,excluded,exclude block,
first-failure,2025-06-05T16:28:41-04:00,2025-06-05T16:28:42-04:00,failed,run error,
first-success,2025-06-05T16:28:41-04:00,2025-06-05T16:28:41-04:00,succeeded,,
second-failure,2025-06-05T16:28:41-04:00,2025-06-05T16:28:42-04:00,failed,run error,
second-success,2025-06-05T16:28:41-04:00,2025-06-05T16:28:41-04:00,succeeded,,
second-early-exit,2025-06-05T16:28:42-04:00,2025-06-05T16:28:42-04:00,early exit,run error,
first-early-exit,2025-06-05T16:28:42-04:00,2025-06-05T16:28:42-04:00,early exit,run error,

That report offers details on the outcome of each run in the Run Queue.

For more information, read the documentation on the Run Report.

What's Changed

Full Changelog: gruntwork-io/terragrunt@v0.81.1...v0.81.2

v0.81.1

Compare Source

🧪 Experiments Added

The reports experiment has been added

As part of delivering #​3628 , the reports experiment has been added.

When enabled, Terragrunt will emit summaries of runs at the end of run --all commands.

e.g.

$ terragrunt run --all plan

### Omitted for brevity...

❯❯ Run Summary
   Duration:   62ms
   Units:      3
   Succeeded:  3

The summary can also be disabled using the --summary-disable flag, even when the experiment is active.

You can learn more about this feature here.

More will be added in the near future to allow for report generation and customization. Stay tuned!

What's Changed

Full Changelog: gruntwork-io/terragrunt@v0.81.0...v0.81.1

v0.81.0

Compare Source

🛠️ Breaking Changes

Bare Includes Deprecated

Use of bare includes (include configuration blocks without a label) are now deprecated.

For example:

include {
    path = find_in_parent_folders("root.hcl")
}

Will now result in a deprecation warning, while the following usage of an include with a label added won't:

include "root" {
    path = find_in_parent_folders("root.hcl")
}

Using labeled includes result in better performance, as backwards compatibility requires that Terragrunt does additional work during configuration processing. You are advised to update your bare includes to use labels as early as possible.

Note that although this deprecation won't be an immediate breaking change. It will be a breaking change in the future. To opt-in to this breaking change today, you can use the bare-include strict control to mandate usage of the modern, labelled include. Doing so will ensure that you and your teammates are leveraging the most performant version of the configuration block.

Backwards compatibility is guaranteed to remain present for this functionality until at least Terragrunt 2.0.

Logging Moved from Terragrunt Options

If you depend on Terragrunt as a Golang library, you'll want to take note that this release introduces a breaking change to public functions in multiple packages to adjust how the logger is passed. The Terragrunt logger is no longer a member of the TerragruntOptions struct in the options package, and is instead passed explicitly as an argument to functions that need the logger.

For example, the signature for the RunCommand function in the shell package changed from this:

func RunCommand(ctx context.Context, opts *options.TerragruntOptions, command string, args ...string) error

To this:

func RunCommand(ctx context.Context, l log.Logger, opts *options.TerragruntOptions, command string, args ...string) error

You maybe need to manually construct a logger to pass into public functions you are calling in Terragrunt packages as a consequence.

✨ New Features

Added constraint_check HCL Function

A new HCL function, constraint_check, has been added to Terragrunt.

This HCL function allows you to drive logic in your configurations based on constraints checked against arbitrary semantic versions.

For example:

feature "module_version" {
  default = "1.2.3"
}

locals {
  module_version       = feature.module_version.value
  needs_v2_adjustments = constraint_check(local.module_version, ">= 2.0.0")
}

terraform {
  source = "github.com/my-org/my-module.git//?ref=v${local.module_version}"
}

inputs = !local.needs_v2_adjustments ? {
  old_module_input_name = "old_module_input_value"
} : {
  new_module_input_name = "new_module_input_value"
}

Using this function, you can alter the behavior of units when particular OpenTofu/Terraform module versions are used, including changing inputs or altering error handling.

🐛 Bugs Introduced

Terragrunt Catalog Scaffolding Panics

A refactor of internal logging caused a panic during scaffolding while using the Terragrunt Catalog Terminal User Interface (TUI) (#​4422), this has since been remediated in v0.81.6.

If you are using the Terragrunt Catalog TUI, you are advised to upgrade to v0.81.6.

What's Changed

Full Changelog: gruntwork-io/terragrunt@v0.80.4...v0.81.0

v0.80.4

Compare Source

✨ New Features

The exec command now supports --tf-path

The exec command has gained support for use of the --tf-path flag. This can be important when Terragrunt incidentally uses OpenTofu/Terraform to do things like fetch outputs from dependencies.

Thanks to @​erpel for contributing this feature!

What's Changed

Full Changelog: gruntwork-io/terragrunt@v0.80.3...v0.80.4

v0.80.3

Compare Source

🏎️ Performance Improvements

Significant performance improvements for run --all

The performance of run --all has been improved in two significant ways:

  1. Performance for named includes has improved.

    Backwards compatibility for bare includes required that Terragrunt do some inefficient work internally to handle both named includes and bare includes by doing an in-memory rewrite of Terragrunt configurations. An optimization has been introduced to avoid this behavior when users use named includes. This optimization does not extend to users that are using bare includes.

    Users are advised to avoid using bare includes whenever possible for maximum performance. A strict control has been introduced to enforce usage of named includes.

    In a future minor release, a warning will be emitted, instructing users to stop using bare includes. Maintainers will avoid breaking support for bare includes until at least 2.0.

    For more information on how to benefit from this optimization, see the migration guide.

  2. The check for OpenTofu/Terraform code has been optimized.

    To provide helpful error messages when users don't have OpenTofu/Terraform code for Terragrunt to run, Terragrunt checks for the presence of OpenTofu/Terraform configuration files (e.g. *.tf, *.tofu). This check has been optimized to improve performance.

In a micro-benchmark on an M3 Max, using the BenchmarkManyEmptyTerragruntInits benchmark, which tests the performance of a Terragrunt run --all init across 1000 inits, the following performance gains were released:

  • 42% speed improvement.
  • 43% memory reduction.

More optimizations of this sort are planned for future releases.

Size reduction of compiled binaries

The size of compiled binaries will be reduced due to the stripping of debug symbols from the final executable. As an example, this drops the size of the compiled Linux AMD64 binary from 99MB to 70MB.

This can be a small improvement to download times for environments where Terragrunt is downloaded frequently.

🐛 Bug Fixes

Fixed -detailed-exitcode behavior in run --all

An unintended side-effect of addressing a different bug for Terragrunt’s handling of the -detailed-exitcode flag in OpenTofu/Terraform in retries was that any run in a run --all could override the exit code of the entire run --all.

This has been fixed. The exit code of the run --all -- plan -detailed-exitcode command will now properly aggregate exit codes from all runs in a run --all, only reseting the exit code for an individual unit if it properly recovers after a retry.

What's Changed

Full Changelog: gruntwork-io/terragrunt@v0.80.2...v0.80.3

v0.80.2

Compare Source

✨ New Features

find adds support for --include

The find command now supports the --include flag to allow for fine grained control over the discovery of units that include other partial configurations.

e.g.

$ terragrunt find --include --format=json | jq
[
  {
    "type": "unit",
    "path": "bar",
    "include": {
      "cloud": "cloud.hcl"
    }
  },
  {
    "type": "unit",
    "path": "foo"
  }
]

Combining the flag with tools like jq allows for simple discovery of configurations that include other partial configurations.

$ terragrunt find --include --format=json | jq '[.[] | select(.include.cloud == "cloud.hcl")]'
[
  {
    "type": "unit",
    "path": "bar",
    "include": {
      "cloud": "cloud.hcl"
    }
  }
]

🐛 Bug Fixes

--tf-path now correctly overrides terraform_binary

A bug in the precedence logic for Terragrunt configuration parsing resulted in the CLI flag --tf-path from being ignored when the terraform_binary attribute was set.

Terragrunt will now correctly respect the terraform_binary attribute when set, and allow --tf-path to override the value when it is set.

What's Changed

Full Changelog: gruntwork-io/terragrunt@v0.80.1...v0.80.2

v0.80.1

Compare Source

What's Changed

Full Changelog: gruntwork-io/terragrunt@v0.80.0...v0.80.1

v0.80.0

Compare Source

Terraform 1.12 support: We are now testing Terragrunt against Terraform 1.12 and is confirmed to be working.

NOTE: Although this release is marked as backward incompatible, it is functionally compatible as nothing has been changed in Terragrunt internals. The minor version release is useful to mark the change in Terraform version that is being tested.

What's Changed

Full Changelog: gruntwork-io/terragrunt@v0.79.3...v0.80.0

v0.79.3

Compare Source

💪🏽 Enhancements

Limitation on Catalog URLs lifted

A limitation on only supporting recognized go-getter URL patters has been lifted from the catalog command.

The reason this limitation existed in the past was to ensure that users were able to have Terragrunt load module source code in browsers from the catalog Terminal User Interface (TUI). To support that, only a constrained set of sources were supported, to ensure that a button was available to pop open the link in the browser.

image image

Terragrunt will now dynamically adjust the buttons available after module selection to gracefully degrade the experience, instead of completely rejecting repository sources that can't be predictably converted to browser URLs.

image

This allows more users to adopt the Terragrunt Catalog, while providing the same great user experience for users that are on fully supported platforms, like GitHub, GitLab, BitBucket, etc.

What's Changed

New Contributors

Full Changelog: gruntwork-io/terragrunt@v0.79.2...v0.79.3

v0.79.2

Compare Source

🏎️ Performance Improvements

Improved overall performance by memoizing -version output in each unit.

In a micro-benchmark on an M3 Max, using the BenchmarkManyEmptyTerragruntInits benchmark, which tests the performance of a T

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate bot changed the title Update dependency gruntwork-io/terragrunt to v0.72.2 Update dependency gruntwork-io/terragrunt to v0.72.3 Jan 21, 2025
@renovate renovate bot force-pushed the renovate/gruntwork-io-terragrunt-0.x branch from 052b08f to 2cfcb89 Compare January 21, 2025 21:54
@renovate renovate bot changed the title Update dependency gruntwork-io/terragrunt to v0.72.3 Update dependency gruntwork-io/terragrunt to v0.72.4 Jan 23, 2025
@renovate renovate bot force-pushed the renovate/gruntwork-io-terragrunt-0.x branch from 2cfcb89 to 5bb757d Compare January 23, 2025 22:01
@renovate renovate bot changed the title Update dependency gruntwork-io/terragrunt to v0.72.4 Update dependency gruntwork-io/terragrunt to v0.72.5 Jan 27, 2025
@renovate renovate bot force-pushed the renovate/gruntwork-io-terragrunt-0.x branch from 5bb757d to 625f376 Compare January 27, 2025 16:30
@renovate renovate bot changed the title Update dependency gruntwork-io/terragrunt to v0.72.5 Update dependency gruntwork-io/terragrunt to v0.72.6 Feb 1, 2025
@renovate renovate bot force-pushed the renovate/gruntwork-io-terragrunt-0.x branch from 625f376 to 6c331c6 Compare February 1, 2025 20:30
@renovate renovate bot changed the title Update dependency gruntwork-io/terragrunt to v0.72.6 Update dependency gruntwork-io/terragrunt to v0.72.8 Feb 7, 2025
@renovate renovate bot force-pushed the renovate/gruntwork-io-terragrunt-0.x branch from 6c331c6 to 5230acc Compare February 7, 2025 17:30
@renovate renovate bot changed the title Update dependency gruntwork-io/terragrunt to v0.72.8 Update dependency gruntwork-io/terragrunt to v0.72.9 Feb 8, 2025
@renovate renovate bot force-pushed the renovate/gruntwork-io-terragrunt-0.x branch 2 times, most recently from 04b1742 to dcba77e Compare February 11, 2025 01:00
@renovate renovate bot changed the title Update dependency gruntwork-io/terragrunt to v0.72.9 Update dependency gruntwork-io/terragrunt to v0.73.0 Feb 11, 2025
@renovate renovate bot changed the title Update dependency gruntwork-io/terragrunt to v0.73.0 Update dependency gruntwork-io/terragrunt to v0.73.1 Feb 12, 2025
@renovate renovate bot force-pushed the renovate/gruntwork-io-terragrunt-0.x branch from dcba77e to 9a071c3 Compare February 12, 2025 14:38
@renovate renovate bot changed the title Update dependency gruntwork-io/terragrunt to v0.73.1 Update dependency gruntwork-io/terragrunt to v0.73.2 Feb 13, 2025
@renovate renovate bot force-pushed the renovate/gruntwork-io-terragrunt-0.x branch from 9a071c3 to f424dcb Compare February 13, 2025 23:22
@renovate renovate bot changed the title Update dependency gruntwork-io/terragrunt to v0.73.2 Update dependency gruntwork-io/terragrunt to v0.73.4 Feb 14, 2025
@renovate renovate bot force-pushed the renovate/gruntwork-io-terragrunt-0.x branch 2 times, most recently from dbb25b5 to a345a96 Compare February 14, 2025 22:02
@renovate renovate bot changed the title Update dependency gruntwork-io/terragrunt to v0.73.4 Update dependency gruntwork-io/terragrunt to v0.73.5 Feb 14, 2025
@renovate renovate bot force-pushed the renovate/gruntwork-io-terragrunt-0.x branch from a345a96 to ab34048 Compare February 15, 2025 21:33
@renovate renovate bot changed the title Update dependency gruntwork-io/terragrunt to v0.73.5 Update dependency gruntwork-io/terragrunt to v0.73.6 Feb 15, 2025
@renovate renovate bot changed the title Update dependency gruntwork-io/terragrunt to v0.73.6 Update dependency gruntwork-io/terragrunt to v0.73.7 Feb 18, 2025
@renovate renovate bot force-pushed the renovate/gruntwork-io-terragrunt-0.x branch from ab34048 to 32389b7 Compare February 18, 2025 19:40
@renovate renovate bot changed the title Update dependency gruntwork-io/terragrunt to v0.73.7 Update dependency gruntwork-io/terragrunt to v0.73.8 Feb 20, 2025
@renovate renovate bot force-pushed the renovate/gruntwork-io-terragrunt-0.x branch from 32389b7 to 7478dc6 Compare February 20, 2025 16:33
@renovate renovate bot changed the title Update dependency gruntwork-io/terragrunt to v0.73.8 Update dependency gruntwork-io/terragrunt to v0.73.9 Feb 21, 2025
@renovate renovate bot force-pushed the renovate/gruntwork-io-terragrunt-0.x branch from 7478dc6 to ee16f34 Compare February 21, 2025 13:49
@renovate renovate bot force-pushed the renovate/gruntwork-io-terragrunt-0.x branch 2 times, most recently from 04fc704 to 8553cc9 Compare June 9, 2025 16:56
@renovate renovate bot changed the title Update dependency gruntwork-io/terragrunt to v0.81.0 Update dependency gruntwork-io/terragrunt to v0.81.1 Jun 9, 2025
@renovate renovate bot changed the title Update dependency gruntwork-io/terragrunt to v0.81.1 Update dependency gruntwork-io/terragrunt to v0.81.3 Jun 10, 2025
@renovate renovate bot force-pushed the renovate/gruntwork-io-terragrunt-0.x branch 2 times, most recently from 83994f7 to ab96e91 Compare June 11, 2025 17:52
@renovate renovate bot changed the title Update dependency gruntwork-io/terragrunt to v0.81.3 Update dependency gruntwork-io/terragrunt to v0.81.4 Jun 11, 2025
@renovate renovate bot force-pushed the renovate/gruntwork-io-terragrunt-0.x branch from ab96e91 to c54cd4e Compare June 11, 2025 23:37
@renovate renovate bot changed the title Update dependency gruntwork-io/terragrunt to v0.81.4 Update dependency gruntwork-io/terragrunt to v0.81.5 Jun 11, 2025
@renovate renovate bot changed the title Update dependency gruntwork-io/terragrunt to v0.81.5 Update dependency gruntwork-io/terragrunt to v0.81.6 Jun 13, 2025
@renovate renovate bot force-pushed the renovate/gruntwork-io-terragrunt-0.x branch 2 times, most recently from 8869dc4 to bb9d887 Compare June 16, 2025 21:55
@renovate renovate bot changed the title Update dependency gruntwork-io/terragrunt to v0.81.6 Update dependency gruntwork-io/terragrunt to v0.81.7 Jun 16, 2025
@renovate renovate bot force-pushed the renovate/gruntwork-io-terragrunt-0.x branch from bb9d887 to 2967d98 Compare June 19, 2025 19:38
@renovate renovate bot changed the title Update dependency gruntwork-io/terragrunt to v0.81.7 Update dependency gruntwork-io/terragrunt to v0.81.8 Jun 19, 2025
@renovate renovate bot force-pushed the renovate/gruntwork-io-terragrunt-0.x branch from 2967d98 to 97540cf Compare June 20, 2025 17:42
@renovate renovate bot changed the title Update dependency gruntwork-io/terragrunt to v0.81.8 Update dependency gruntwork-io/terragrunt to v0.81.10 Jun 20, 2025
@renovate renovate bot force-pushed the renovate/gruntwork-io-terragrunt-0.x branch from 97540cf to a41356e Compare June 25, 2025 14:44
@renovate renovate bot changed the title Update dependency gruntwork-io/terragrunt to v0.81.10 Update dependency gruntwork-io/terragrunt to v0.82.0 Jun 25, 2025
@renovate renovate bot force-pushed the renovate/gruntwork-io-terragrunt-0.x branch from a41356e to c40ec19 Compare June 26, 2025 13:00
@renovate renovate bot changed the title Update dependency gruntwork-io/terragrunt to v0.82.0 Update dependency gruntwork-io/terragrunt to v0.82.1 Jun 26, 2025
@renovate renovate bot force-pushed the renovate/gruntwork-io-terragrunt-0.x branch from c40ec19 to 7b99b03 Compare June 27, 2025 01:45
@renovate renovate bot changed the title Update dependency gruntwork-io/terragrunt to v0.82.1 Update dependency gruntwork-io/terragrunt to v0.82.2 Jun 27, 2025
@renovate renovate bot changed the title Update dependency gruntwork-io/terragrunt to v0.82.2 Update dependency gruntwork-io/terragrunt to v0.82.3 Jun 27, 2025
@renovate renovate bot force-pushed the renovate/gruntwork-io-terragrunt-0.x branch 2 times, most recently from fc287f9 to c2a3462 Compare July 2, 2025 14:55
@renovate renovate bot changed the title Update dependency gruntwork-io/terragrunt to v0.82.3 Update dependency gruntwork-io/terragrunt to v0.82.4 Jul 2, 2025
@renovate renovate bot force-pushed the renovate/gruntwork-io-terragrunt-0.x branch from c2a3462 to 981f35c Compare July 4, 2025 19:44
@renovate renovate bot changed the title Update dependency gruntwork-io/terragrunt to v0.82.4 Update dependency gruntwork-io/terragrunt to v0.83.0 Jul 4, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
0 participants