Skip to content

chore(deps): update dependency gruntwork-io/terragrunt to v0.81.5 (dockerfile) (main) #121

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
ivankatliarchuk wants to merge 1 commit into
base: main
Choose a base branch
from
Open

chore(deps): update dependency gruntwork-io/terragrunt to v0.81.5 (dockerfile) (main) #121

ivankatliarchuk wants to merge 1 commit into from

Conversation

@ivankatliarchuk
Copy link
Member

@ivankatliarchuk ivankatliarchuk commented Mar 25, 2024 •
edited
Loading

This PR contains the following updates:

Package Update Change Pending
gruntwork-io/terragrunt minor 0.45.3 -> 0.81.5 v0.81.6
gruntwork-io/terragrunt minor 0.45.3 -> 0.81.5 0.81.6

Warning

Some dependencies could not be looked up. Check the warning logs for more information.

Release Notes

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

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 Terragrunt run --all init across 1000 units, the following performance gains were released:

  • 18% speed improvement.
  • 9% memory reduction.

More optimizations of this sort are planned for future releases.

What's Changed

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

v0.79.1

Compare Source

💪🏽 Enhancements
Recursive stack clean

Improved stack clean to recursively delete all nested stack directories, ensuring thorough cleanup.

What's Changed

Full Changelog: gruntwork-io/terragrunt@v0.79.0...v0.79.1

v0.79.0

Compare Source

💪🏽 Enhancements
The run --all command automatically generates Terragrunt Stacks

If you are using terragrunt.stack.hcl files in your codebase, run --all commands will now automatically expand all terragrunt.stack.hcl files into generated stack configurations, as if you had run stack generate before running the run --all command.

e.g.

terragrunt run --all plan

Is now equivalent to:

terragrunt stack generate
terragrunt run --all plan

If you would like to disable this new behavior, you can use the --no-stack-generate to opt out of automatic stack generation.

📖 Docs Updates

The Terragrunt v1 docs are open for feedback!

These docs will undergo significant adjustments, both stylistically, and functionality on the road to 1.0.

They are a full rewrite of the existing Terragrunt Docs site written in Jekyll to one using Starlight.

Your feedback is requested! If you are reading these release notes relatively soon after release, you should see a link at the top of the site where you can provide your feedback on the new docs.

What's Changed
New Contributors

Full Changelog: gruntwork-io/terragrunt@v0.78.4...v0.79.0

v0.78.4

Compare Source

✨ New Features
OpenTelemetry Trace Propogation

In anticipation of the introduction of OpenTelemetry support in OpenTofu 1.10, Terragrunt will now propagate the TRACEPARENT environment variable to child processes to support OpenTelemetry traces that maintain context across Terragrunt and OpenTofu.

This work is based on @​Yantrio 's PoC PR #​4254, and is only useful due to his work adding OpenTelemtry in OpenTofu. Thank you!

What's Changed

Full Changelog: gruntwork-io/terragrunt@v0.78.3...v0.78.4

v0.78.3

Compare Source

🐛 Bug Fixes

When an error retry results in a plan succeeding when it initially failed, usage of run --all -- plan -detailed-exitcode will now properly take into account the final exit code, rather than the first one, meaning that the exit code of the whole run will be zero if no other units fail their plans.

Thanks to @​wakeful for contributing this fix!

What's Changed

Full Changelog: gruntwork-io/terragrunt@v0.78.2...v0.78.3

v0.78.2

Compare Source

What's Changed

Full Changelog: gruntwork-io/terragrunt@v0.78.1...v0.78.2

v0.78.1

Compare Source

What's Changed

Full Changelog: gruntwork-io/terragrunt@v0.78.0...v0.78.1

v0.78.0

Compare Source

🧪 Experiments Completed

The stacks experiment is now complete.

If you were previously using the flag --experiment stacks to opt in to experimental functionality, you no longer have to do so. Note that if you are, you will simply get a warning that it is no longer necessary.

🛠️ Breaking Changes

Legacy commands (as replaced by the CLI Redesign are now deprecated, and will be phased out at a future date, which will be scheduled in #​3535. Make sure to subscribe to the issue if you would like to be informed when these deprecated features are no longer supported.

For instructions on migrating to the new commands provided after the CLI Redesign, read the CLI Redesign Migration Guide.

The following are now deprecated:

  • hclfmt (use hcl fmt instead)
  • hclvalidate (use hcl validate instead)
  • validate-inputs (use hcl validate --inputs and hcl validate --inputs --strict instead)
  • terragrunt-info (use info print instead)
  • output-module-groups (use find --dag --json instead)
  • render-json (use render --json -w instead)
  • graph-dependencies (use dag graph instead)
  • run-all (use run --all instead)
  • graph (use run --graph instead)
  • The default command. e.g. terragrunt workspace list (use terragrunt run -- workspace list instead)
  • Default bootstrap (automatically provisioning backend resources without additional flags). This is now opt in behavior, and requires usage of the --backend-bootstrap flag or explicitly running the new backend bootstrap command.
  • aws-provider-patch (we are simply deprecating this command, and removing it when the other commands are removed. It served its purpose as a short term stopgap tool).

Note that this will not result in an immediate breaking change for users, as we’ll have an initial deprecation window to give users time to adjust to these changes. If you’d like to ensure that you are prepared for the future removal of legacy commands, you can take advantage of the cli-redesign strict control to opt in to the future breaking change early.

💪🏽 Enhancements

The logging for stack generation has been improved to make it easier to determine at a glance the stack file that’s generating a particular unit.

stacks-generation

What's Changed

Full Changelog: gruntwork-io/terragrunt@v0.77.22...v0.78.0

v0.77.22

Compare Source

🧪 Experiments Completed
The cli-redesign experiment is now complete

The cli-redesign experiment is now complete.

If you were previously using the flag --experiment cli-redesign to opt in to experimental functionality, you no longer have to do so. Note that if you are, you will simply get a warning that it is no longer necessary.

What's Changed

Full Changelog: gruntwork-io/terragrunt@v0.77.21...v0.77.22

v0.77.21

Compare Source

✨ New Features
Introduction of hcl commands

As part of the CLI Redesign experiment, the hcl commands have been introduced.

The hcl commands allow users to directly interact with HCL content independent of the underlying functionality they support.

The functionality of the hcl commands replace existing functionality that is soon to be deprecated:

  • hclfmt --> hcl fmt
  • hclvalidate --> hcl validate
  • validate-inputs --> hcl validate --inputs
  • validate-inputs --strict-validate --> hcl validate --inputs --strict
What's Changed

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 is behind base branch, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

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

This PR has been generated by Renovate Bot.

@ivankatliarchuk ivankatliarchuk self-assigned this Mar 25, 2024
@ivankatliarchuk ivankatliarchuk force-pushed the renovate/main-gruntwork-io-terragrunt-0.x branch from b90dc05 to 2ab6e20 Compare March 25, 2024 04:33
@github-actions
Copy link

github-actions bot commented Mar 25, 2024

@ivankatliarchuk: There are no 'kind' label on this PR. You need a 'kind' label.
Label can be added by writing in a comment ⬇️

  • /kind feature
  • /kind fix
  • /kind chore
  • /kind docs
  • /kind refactor
  • /kind github
  • /kind security
  • /kind question
Details

I am a bot created to help the cloudkats developers manage community feedback and contributions. You can check out my manifest file to understand my behavior and what I can do. If you want to use this for your project, you can check out the DeFiCh/oss-governance-bot repository.

@ivankatliarchuk ivankatliarchuk force-pushed the renovate/main-gruntwork-io-terragrunt-0.x branch from 2ab6e20 to 7a008d3 Compare March 26, 2024 04:21
@ivankatliarchuk ivankatliarchuk changed the title chore(deps): update dependency gruntwork-io/terragrunt to v0.55.18 (dockerfile) (main) chore(deps): update dependency gruntwork-io/terragrunt to v0.55.19 (dockerfile) (main) Mar 26, 2024
@ivankatliarchuk ivankatliarchuk force-pushed the renovate/main-gruntwork-io-terragrunt-0.x branch from 7a008d3 to 0741d9e Compare March 28, 2024 23:02
@ivankatliarchuk ivankatliarchuk changed the title chore(deps): update dependency gruntwork-io/terragrunt to v0.55.19 (dockerfile) (main) chore(deps): update dependency gruntwork-io/terragrunt to v0.55.20 (dockerfile) (main) Mar 28, 2024
@ivankatliarchuk ivankatliarchuk force-pushed the renovate/main-gruntwork-io-terragrunt-0.x branch from 0741d9e to 191e2eb Compare April 5, 2024 20:09
@ivankatliarchuk ivankatliarchuk changed the title chore(deps): update dependency gruntwork-io/terragrunt to v0.55.20 (dockerfile) (main) chore(deps): update dependency gruntwork-io/terragrunt to v0.55.21 (dockerfile) (main) Apr 5, 2024
@ivankatliarchuk ivankatliarchuk force-pushed the renovate/main-gruntwork-io-terragrunt-0.x branch from 191e2eb to 55eebd3 Compare April 8, 2024 04:26
@ivankatliarchuk ivankatliarchuk changed the title chore(deps): update dependency gruntwork-io/terragrunt to v0.55.21 (dockerfile) (main) chore(deps): update dependency gruntwork-io/terragrunt to v0.56.2 (dockerfile) (main) Apr 8, 2024
@ivankatliarchuk ivankatliarchuk force-pushed the renovate/main-gruntwork-io-terragrunt-0.x branch from 55eebd3 to 1bee8a2 Compare April 12, 2024 04:20
@ivankatliarchuk ivankatliarchuk changed the title chore(deps): update dependency gruntwork-io/terragrunt to v0.56.2 (dockerfile) (main) chore(deps): update dependency gruntwork-io/terragrunt to v0.56.3 (dockerfile) (main) Apr 12, 2024
@ivankatliarchuk ivankatliarchuk force-pushed the renovate/main-gruntwork-io-terragrunt-0.x branch from 1bee8a2 to 82bd362 Compare April 14, 2024 04:44
@ivankatliarchuk ivankatliarchuk changed the title chore(deps): update dependency gruntwork-io/terragrunt to v0.56.3 (dockerfile) (main) chore(deps): update dependency gruntwork-io/terragrunt to v0.56.5 (dockerfile) (main) Apr 14, 2024
@ivankatliarchuk ivankatliarchuk force-pushed the renovate/main-gruntwork-io-terragrunt-0.x branch from 82bd362 to 3b88dad Compare April 16, 2024 04:23
@ivankatliarchuk ivankatliarchuk changed the title chore(deps): update dependency gruntwork-io/terragrunt to v0.56.5 (dockerfile) (main) chore(deps): update dependency gruntwork-io/terragrunt to v0.57.0 (dockerfile) (main) Apr 16, 2024
@ivankatliarchuk ivankatliarchuk force-pushed the renovate/main-gruntwork-io-terragrunt-0.x branch from 3b88dad to 482bb81 Compare April 19, 2024 04:27
@ivankatliarchuk ivankatliarchuk changed the title chore(deps): update dependency gruntwork-io/terragrunt to v0.57.0 (dockerfile) (main) chore(deps): update dependency gruntwork-io/terragrunt to v0.57.1 (dockerfile) (main) Apr 19, 2024
@ivankatliarchuk ivankatliarchuk force-pushed the renovate/main-gruntwork-io-terragrunt-0.x branch from 482bb81 to 0b9a359 Compare April 20, 2024 04:28
@ivankatliarchuk ivankatliarchuk changed the title chore(deps): update dependency gruntwork-io/terragrunt to v0.57.1 (dockerfile) (main) chore(deps): update dependency gruntwork-io/terragrunt to v0.57.2 (dockerfile) (main) Apr 20, 2024
@ivankatliarchuk ivankatliarchuk force-pushed the renovate/main-gruntwork-io-terragrunt-0.x branch from 0b9a359 to f955a8b Compare April 23, 2024 04:30
@ivankatliarchuk ivankatliarchuk changed the title chore(deps): update dependency gruntwork-io/terragrunt to v0.57.2 (dockerfile) (main) chore(deps): update dependency gruntwork-io/terragrunt to v0.57.5 (dockerfile) (main) Apr 23, 2024
@ivankatliarchuk ivankatliarchuk changed the title chore(deps): update dependency gruntwork-io/terragrunt to v0.77.20 (dockerfile) (main) chore(deps): update dependency gruntwork-io/terragrunt to v0.77.22 (dockerfile) (main) Apr 25, 2025
@ivankatliarchuk ivankatliarchuk force-pushed the renovate/main-gruntwork-io-terragrunt-0.x branch from e7854c0 to 9657443 Compare May 5, 2025 18:38
@ivankatliarchuk ivankatliarchuk changed the title chore(deps): update dependency gruntwork-io/terragrunt to v0.77.22 (dockerfile) (main) chore(deps): update dependency gruntwork-io/terragrunt to v0.78.0 (dockerfile) (main) May 5, 2025
@ivankatliarchuk ivankatliarchuk force-pushed the renovate/main-gruntwork-io-terragrunt-0.x branch from 9657443 to b827a4c Compare May 10, 2025 04:27
@ivankatliarchuk ivankatliarchuk changed the title chore(deps): update dependency gruntwork-io/terragrunt to v0.78.0 (dockerfile) (main) chore(deps): update dependency gruntwork-io/terragrunt to v0.78.1 (dockerfile) (main) May 10, 2025
@ivankatliarchuk ivankatliarchuk force-pushed the renovate/main-gruntwork-io-terragrunt-0.x branch from b827a4c to 8e889ad Compare May 13, 2025 04:29
@ivankatliarchuk ivankatliarchuk changed the title chore(deps): update dependency gruntwork-io/terragrunt to v0.78.1 (dockerfile) (main) chore(deps): update dependency gruntwork-io/terragrunt to v0.78.2 (dockerfile) (main) May 13, 2025
@ivankatliarchuk ivankatliarchuk force-pushed the renovate/main-gruntwork-io-terragrunt-0.x branch from 8e889ad to 71d5d7e Compare May 16, 2025 04:32
@ivankatliarchuk ivankatliarchuk changed the title chore(deps): update dependency gruntwork-io/terragrunt to v0.78.2 (dockerfile) (main) chore(deps): update dependency gruntwork-io/terragrunt to v0.78.3 (dockerfile) (main) May 16, 2025
@ivankatliarchuk ivankatliarchuk force-pushed the renovate/main-gruntwork-io-terragrunt-0.x branch from 71d5d7e to 9960116 Compare May 17, 2025 04:30
@ivankatliarchuk ivankatliarchuk changed the title chore(deps): update dependency gruntwork-io/terragrunt to v0.78.3 (dockerfile) (main) chore(deps): update dependency gruntwork-io/terragrunt to v0.78.4 (dockerfile) (main) May 17, 2025
@ivankatliarchuk ivankatliarchuk force-pushed the renovate/main-gruntwork-io-terragrunt-0.x branch from 9960116 to cd3b34a Compare May 24, 2025 04:30
@ivankatliarchuk ivankatliarchuk changed the title chore(deps): update dependency gruntwork-io/terragrunt to v0.78.4 (dockerfile) (main) chore(deps): update dependency gruntwork-io/terragrunt to v0.79.0 (dockerfile) (main) May 24, 2025
@ivankatliarchuk ivankatliarchuk force-pushed the renovate/main-gruntwork-io-terragrunt-0.x branch from cd3b34a to 54862b6 Compare May 25, 2025 04:35
@ivankatliarchuk ivankatliarchuk changed the title chore(deps): update dependency gruntwork-io/terragrunt to v0.79.0 (dockerfile) (main) chore(deps): update dependency gruntwork-io/terragrunt to v0.80.0 (dockerfile) (main) May 25, 2025
@ivankatliarchuk ivankatliarchuk force-pushed the renovate/main-gruntwork-io-terragrunt-0.x branch from 54862b6 to b413086 Compare May 26, 2025 04:35
@ivankatliarchuk ivankatliarchuk changed the title chore(deps): update dependency gruntwork-io/terragrunt to v0.80.0 (dockerfile) (main) chore(deps): update dependency gruntwork-io/terragrunt to v0.80.2 (dockerfile) (main) May 26, 2025
@ivankatliarchuk ivankatliarchuk force-pushed the renovate/main-gruntwork-io-terragrunt-0.x branch from b413086 to 1757132 Compare May 31, 2025 04:32
@ivankatliarchuk ivankatliarchuk changed the title chore(deps): update dependency gruntwork-io/terragrunt to v0.80.2 (dockerfile) (main) chore(deps): update dependency gruntwork-io/terragrunt to v0.80.3 (dockerfile) (main) May 31, 2025
@ivankatliarchuk ivankatliarchuk force-pushed the renovate/main-gruntwork-io-terragrunt-0.x branch from 1757132 to 9f66eca Compare June 1, 2025 04:41
@ivankatliarchuk ivankatliarchuk changed the title chore(deps): update dependency gruntwork-io/terragrunt to v0.80.3 (dockerfile) (main) chore(deps): update dependency gruntwork-io/terragrunt to v0.80.4 (dockerfile) (main) Jun 1, 2025
@ivankatliarchuk ivankatliarchuk force-pushed the renovate/main-gruntwork-io-terragrunt-0.x branch from 9f66eca to dc8c9f5 Compare June 6, 2025 04:35
@ivankatliarchuk ivankatliarchuk changed the title chore(deps): update dependency gruntwork-io/terragrunt to v0.80.4 (dockerfile) (main) chore(deps): update dependency gruntwork-io/terragrunt to v0.81.0 (dockerfile) (main) Jun 6, 2025
@ivankatliarchuk ivankatliarchuk force-pushed the renovate/main-gruntwork-io-terragrunt-0.x branch from dc8c9f5 to 9358e07 Compare June 13, 2025 04:38
@ivankatliarchuk ivankatliarchuk changed the title chore(deps): update dependency gruntwork-io/terragrunt to v0.81.0 (dockerfile) (main) chore(deps): update dependency gruntwork-io/terragrunt to v0.81.1 (dockerfile) (main) Jun 13, 2025
@ivankatliarchuk ivankatliarchuk force-pushed the renovate/main-gruntwork-io-terragrunt-0.x branch from 9358e07 to 911295c Compare June 14, 2025 04:29
@ivankatliarchuk ivankatliarchuk changed the title chore(deps): update dependency gruntwork-io/terragrunt to v0.81.1 (dockerfile) (main) chore(deps): update dependency gruntwork-io/terragrunt to v0.81.3 (dockerfile) (main) Jun 14, 2025
@ivankatliarchuk ivankatliarchuk force-pushed the renovate/main-gruntwork-io-terragrunt-0.x branch from 911295c to cb6f7bb Compare June 15, 2025 04:36
@ivankatliarchuk ivankatliarchuk changed the title chore(deps): update dependency gruntwork-io/terragrunt to v0.81.3 (dockerfile) (main) chore(deps): update dependency gruntwork-io/terragrunt to v0.81.5 (dockerfile) (main) Jun 15, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

@ivankatliarchuk ivankatliarchuk

Labels

datasource::github-releases deps manager:regex needs/kind renovate Universal dependency update tool rule::1 type::minor

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

2 participants

@ivankatliarchuk