Skip to content

fix(deps): update github (minor) #82

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

fix(deps): update github (minor) #82

renovate wants to merge 1 commit into from

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Feb 24, 2024 •
edited
Loading

Note: This PR body was truncated due to platform limits.

This PR contains the following updates:

Package Change Age Confidence Type Update
github.com/gruntwork-io/terragrunt v0.77.5 → v0.97.0 age confidence require minor
github.com/hashicorp/hcl/v2 v2.23.0 → v2.24.0 age confidence require minor
github.com/hashicorp/terraform-config-inspect a34142e → 225c06e age confidence require digest
github.com/hashicorp/terraform-exec v0.20.0 → v0.24.0 age confidence require minor
github.com/hashicorp/terraform-json v0.21.0 → v0.27.2 age confidence require minor
github.com/jedib0t/go-pretty/v6 v6.5.4 → v6.7.8 age confidence require minor
github.com/savioxavier/termlink v1.3.0 → v1.4.3 age confidence require minor
github.com/spf13/cobra v1.8.1 → v1.10.2 age confidence require minor
github.com/spf13/viper v1.19.0 → v1.21.0 age confidence require minor
github.com/zclconf/go-cty v1.16.2 → v1.17.0 age confidence require minor

Release Notes

gruntwork-io/terragrunt (github.com/gruntwork-io/terragrunt)

v0.97.0

Compare Source

⚒️ Breaking Changes

The --queue-strict-include flag is deprecated

Terragrunt no longer automatically includes dependencies of included units. As such the --queue-strict-include flag is no longer useful in the Terragrunt CLI.

The flag has been deprecated, and no longer does anything. This flag will not be removed before 2.0.

Run report no longer reports --queue-exclude-dir as a reason for exclusion

Run reports no longer report on units excluded from runs as a consequence of the --queue-exclude-dir flag.

The --units-that-include flag is deprecated

The --units-that-include flag is now an alias for the reading= attribute filter, just like the --queue-include-units-reading flag.

Given that the two flags no longer differ in functionality, and that the functionality of the --units-that-include is no longer strictly including units that are included, the flag has been deprecated.

The double-star strict control is complete

The globbing behavior of Terragrunt in CLI flags has been updated to match all paths when ending with a trailing ** .

🧪 Experiments Completed

The filter-flag experiment is completed

The filter-flag experiment is completed, and the --filter flag is now generally available.

You can use filter expressions as a single unified API for controlling the Run Queue, replacing the need to use the following CLI flags:

Legacy —queue flag Equivalent —filter expression
—-queue-include-dir=path —-filter='{./path}'
—-queue-exclude-dir=path —-filter='!{./path}'
--queue-include-units-reading=root.hcl --filter='reading=root.hcl'
--units-that-include=root.hcl --filter='reading=root.hcl'
--queue-include-external-dependencies --filter='{./**}...'
--queue-excludes-file=excludes.txt --filters-file='filters.txt' *
--graph --filter='...{.}'
  • Note that the file used for the --queue-excludes-file does not directly translate to the kind of file you can use for a --filters-file. To learn more, see the documentation.

The table above also explains the aliasing that has been done internally to replace queue flags with their filter equivalents. The aliasing for these queue flags is present purely for backwards compatibility purposes, but they are not going to emit deprecation warnings, and will not be removed before the Terragrunt 1.0 release.

You are heavily encouraged to adopt the new --filter flag for your infrastructure targeting needs as soon as feasible in your workflows. It will offer a significantly more flexible and powerful experience.

To learn more see the Filters feature documentation.

🐛 Bug Fixes

The get_original_terragrunt_dir() function is now supported in terragrunt.stack.hcl files

When authoring explicit stacks, using the get_original_terragrunt_dir() HCL function in terragrunt.stack.hcl files will now return the directory where the terragrunt.stack.hcl file lives, even when the configuration is read from another stack/unit using read_terragrunt_config().

Using Git-based expressions with the --out-dir flag is fixed

When using Git-based expressions using the --filter flag, the relative path of units relative to their respective Git worktree roots is used for determining where the plan file will be saved, rather than a path in the relevant Git worktree.

Color for output fetching is suppressed more reliably

Terragrunt will use tofu output -json / terraform output -json more reliably when users expect a lack of colors (like when colors are suppressed for Terragrunt).

What's Changed

New Contributors

Full Changelog: https://github.com/gruntwork-io/terragrunt/compare/v0.96.1..v.0.97.0

v0.96.1

Compare Source

🧪 Experiments Updated

The --filter-affected flag has more robust determination of the default branch in a Git repository

The --filter-affected flag will now use Git plumbing to interrogate the default branch as considered by the remote repository before falling back to interrogating local configurations for determination of a default branch (remember that you must use the filter-flag experiment to try this out).

# This is checked first
$ git rev-parse --abbrev-ref origin/HEAD

# Followed by this
$ git ls-remote --symref origin HEAD

# Followed with this
$ git config init.defaultBranch

# If none of the above succeed, the default branch is assumed to be `main`.
Git-based filter expressions now warn users when using local state

Usage of --filter Git-based expressions in combination with local state will now emit a warning, recommending usage of remote states (remember that you must use the filter-flag experiment to try this out).

$ terragrunt run --all --filter '[HEAD~1...HEAD]' -- plan
09:30:38.017 WARN   One or more units discovered using Git-based filter expressions (e.g. [HEAD~1...HEAD]) do not have a remote_state configuration. This may result in unexpected outcomes, such as outputs for dependencies returning empty. It is strongly recommended to use remote state when working with Git-based filter expressions.

See the warning at the bottom of Git-based expressions documentation for more information.

OpenTelemetry traces added for filter evaluation

Filter evaluation now emits OpenTelemetry spans and metrics, including filter resolution details, evaluation duration, and filtering scope. This helps teams analyze performance and pinpoint bottlenecks in filtering with large Terragrunt repositories.

filter-otel-traces

🐛 Bug Fixes

Path-based filters targeting external paths fixed

A bug in the parsing of path-based filter expressions in the --filter flag of the filter-flag experiment prevented parsing of path-based filters for external paths (e.g. --filter ../external-dir). This bug has been fixed.

HTTPS Git CAS URLs fixed

A bug in the parsing of source URLs with forced usage of the Git protocol (e.g. git::https://github.com/acme/catalog) prevented using the cas experiment with HTTPS Git URLs with forced usage of the Git protocol. This bug has been fixed.

Regression of support for root terragrunt.hcl fixed

A bug in the processing of --queue-exclude-dir resulted in prefix based matching of non-glob expressions in --queue-exclude-dir values. This broke backwards compatibility for users with a root terragrunt.hcl file instead of a differently named file for the root include (e.g. root.hcl). This bug has been fixed.

Note that you are still advised to migrate away from using a root terragrunt.hcl as soon as possible for your team. We will maintain backwards compatibility until at least 2.0, however.

What's Changed

Full Changelog: gruntwork-io/terragrunt@v0.96.0...v0.96.1

v0.96.0

Compare Source

🛠️ Breaking Changes

The --no-destroy-dependencies-check flag has been deprecated

The default behavior of Terragrunt with respect to checking dependents during destroys has been inverted. As a consequence the --no-destroy-dependencies-check has been deprecated, and a new --destroy-dependencies-check flag has been introduced.

Previously, Terragrunt would automatically parse all configurations that might depend on a unit being destroyed to warn users that the destroyed configuration might orphan other units that depend on it. This was frequently undesirable behavior due to the fact that it introduced additional unnecessary work (parsing all HCL configurations unnecessarily), and could introduce errors if users had unrelated invalid HCL configurations.

Terragrunt now requires that users opt-in to this behavior via the new --destroy-dependencies-check flag, which enables the destroy check, and will not perform the destroy check by default.

terragrunt run --destroy-dependencies-check -- destroy

To learn more, see the no-destroy-dependencies-check strict control.

The --disable-command-validation flag has been deprecated

Terragrunt no longer performs command name validation when passing commands to OpenTofu/Terraform from Terragrunt when using the run command. This makes the --disable-command-validation flag unnecessary, as the lack of validation is now the default behavior.

Previously, Terragrunt had no way to explicitly indicate that a command being used on the Terragrunt CLI was intended as a passthrough to the OpenTofu/Terraform CLI, so it was important that validation be done on the command being supplied on the Terragrunt CLI.

Since completion of the CLI Redesign, this has changed significantly. Users now have explicit shortcuts on the Terragrunt CLI for common OpenTofu/Terraform commands and an explicit interface for passing through OpenTofu/Terraform commands to the OpenTofu/Terraform CLIs using the run command. By removing this validation, Terragrunt will now automatically support new OpenTofu/Terraform commands in future versions of the tools and allow for greater flexibility in IaC Engines, as novel commands can be introduced.

To learn more, see the disable-command-validation strict control.

The --experimental-engine flag now enables the iac-engine experiment

The experimental IaC Engine feature was introduced in Terragrunt prior to the introduction of the experiment system. As such, it wasn’t enabled when users enabled experiment mode, and didn’t have a dedicated section in the experiments docs.

The --experimental-engine flag is now an alias for explicitly enabling the iac-engine experiment, and using IaC Engines will be allowed when using Terragrunt in experiment mode. This increases consistency with how experimental features are managed in Terragrunt, and reduces the surface area users have to be aware of in the Terragrunt CLI.

terragrunt run --experiment=iac-engine

Note that you can explicitly disable usage of engines now with the --no-engine flag, even when the experiment is active.

terragrunt run --experiment=iac-engine --no-engine

To learn more, see the iac-engine experiment.

The --dependency-fetch-output-from-state flag now enables the dependency-fetch-output-from-state experiment

The experimental —dependency-fetch-output-from-state flag was introduced in Terragrunt prior to the introduction of the experiment system. As such, it wasn’t enabled when users enabled experiment mode, and didn’t have a dedicated section in the experiments docs.

The --dependency-fetch-output-from-state flag is now an alias for explicitly enabling the dependency-fetch-output-from-state experiment, and Terragrunt will automatically attempt to fetch outputs from backend state when in experiment mode. This increases consistency with how experimental features are managed in Terragrunt, and reduces the surface area users have to be aware of in the Terragrunt CLI.

terragrunt run --experiment=dependency-fetch-output-from-state

Note that you can explicitly disable fetching output from state with the --no-dependency-fetch-output-from-state flag, even when the experiment is active.

terragrunt run --experiment=dependency-fetch-output-from-state --no-dependency-fetch-output-from-state

To learn more, see the dependency-fetch-output-from-state experiment.

🧪 Experiments Updated

The filter-flag experiment now supports the --filters-file flag

The --filters-file flag has been introduced to allow for the application of multiple filters as defined in a newline-delimited text file, similar to the existing --excludes-file flag (remember that you must use the filter-flag experiment to try this).

 # custom-filters.txt
 !./unstable/**
 $ terragrunt find --filters-file custom-filters.txt
 # No results in `./unstable` discovered.

When the filter-flag experiment is active, Terragrunt will automatically parse and apply filters found in a .terragrunt-filters file, similar to how it automatically parses and applies excludes found in a .terragrunt-excludes file.

 # .terragrunt-filters
 !./unstable/**
# Note that it only does this by default when the experiment is active.
terragrunt find

# Still no results in `./unstable` discovered.

To explicitly disable usage of filter files (including the automatic .terragrunt-filters file), use the --no-filters-file flag.

 # .terragrunt-filters
 !./unstable/**
# Note that it only does this by default when the experiment is active.
terragrunt find --no-filters-file

# This _will_ allow results in `./unstable` to be discovered.

Unlike the --excludes-file, usage of the --filters-file flag also allows for always filtering for particular configurations.

# .terragrunt-filters
./always-include/**

To learn more, see the filters file documentation.

🐛 Bug Fixes

Unnecessary .terragrunt-cache directory no longer generated in run --all runs

Fixed a regression where run --all would create empty .terragrunt-cache directories in the current working directory, even when not needed.

What's Changed

New Contributors

Full Changelog: gruntwork-io/terragrunt@v0.95.1...v0.96.0

v0.95.1

Compare Source

🧪 Experiments Updated

The filter-flag experiment now supports the --filter-affected flag

The --filter-affected flag has been introduced as an convenience alias for --filter [main...HEAD] (remember that you must use the filter-flag experiment to try this).

terragrunt find --filter-affected

Note that if you have local Git configurations that results in a different branch being your default branch, that branch will be used instead of main.

🐛 Bug Fixes

Integration of --queue-strict-include with --queue-include-units-reading fixed

A regression in --queue-strict-include resulted in empty run queues when using a combination of --queue-strict-include with --queue-include-units-reading. That bug has been resolved.

Integration of --source with run --all fixed

A regression in --source prevented it from working correctly in combination with run --all , resulting in empty run queues. That bug has been resolved.

Integration of Git-expressions with explicit stacks

A bug in the implementation of explicit stack generation for Git-expressions prevented stacks from being generated in Git worktrees when using Git-expressions in the filter-flag experiment. That bug has been resolved.

🧹 Chores

Dependencies updates
  • cloud.google.com/go/storage —> v1.58.0
  • github.com/aws/aws-sdk-go-v2 —> v1.41.0
  • github.com/hashicorp/go-version —> v1.8.0
  • github.com/aws/smithy-go —> v1.24.0

What's Changed

Full Changelog: gruntwork-io/terragrunt@v0.95.0...v0.95.1

v0.95.0

Compare Source

🛠️ Breaking Changes

The --queue-exclude-external flag has been deprecated

Previously, Terragrunt would automatically pull in external dependencies (dependencies outside the current working directory when running terragrunt run --all) into the run queue.

To prevent this behavior, users had to manually supply the --queue-exclude-external flag. This has caused significant confusion and unexpected behavior for users over the duration of it’s existence in the Terragrunt CLI. To prevent this unexpected behavior for users and follow the principle of least surprise, this flag has been deprecated and its behavior is now the default in Terragrunt.

To explicitly request inclusion of external dependencies in the run queue, use the —queue-include-external flag.

⚙️ Process Updates

OpenTofu 1.11.x added to compatibility matrix

We are now continuously testing against OpenTofu 1.11.1 in our Continuous Integration testing, and have updated the compatibility matrix to reflect that.

🧪 Updated Experiments

The filter-flag experiment now supports Git-based expressions

The --filter flag can now be used to filter units based on changes in Git history (remember that you must use the filter-flag experiment to try this).

# Compare between two references
terragrunt find --filter '[main...HEAD]'

# Shorthand: compare reference to HEAD
terragrunt find --filter '[main]'

# Compare between specific commits
terragrunt find --filter '[abc123...def456]'

# Compare between tags
terragrunt find --filter '[v1.0.0...v2.0.0]'

# Compare using relative references
terragrunt find --filter '[HEAD~1...HEAD]'

# Compare between branches
terragrunt find --filter '[feature-branch...main]'

For more information, see the dedicated documentation on Git-Based Filtering.

🐛 Bug Fixes

Units now properly flush stdout in run --all

A regression in unit stdout flushing caused stdout for unit logs to hang pending resolution of run --all runs. This regression has been fixed to ensure that logs are streamed in real time again.

Queue entries now properly run, even if dependent units are excluded

A bug in run queue optimization made it so that excluding the dependent of a unit within a multi-unit run queue would incorrectly exclude the dependency unit from the run queue. This bug has been resolved, and units are now properly included, even if their dependents are excluded.

Provider cache server only contacts relevant registries

The provider cache server was incorrectly establishing a connection with multiple registries even though only one registry for a given IaC tool run by Terragrunt. For users with network-restricted environments, this could cause problems. Terragrunt will now only contact the relevant registry for a given IaC tool unless users explicitly request for usage of multiple registries.

📖 Documentation Updates

Provider cache server no longer documented as experimental

The Provider Cache Server has been used in production by a good portion of the Terragrunt community based on voluntary community reporting. The need for the feature is also mitigated by advances in OpenTofu that makes the Automatic Provider Cache Dir the default solution all Terragrunt users using OpenTofu ≥ v1.10.0.

As such, the Provider Cache Server has been promoted to a generally available feature that is exclusively opt-in for users that cannot benefit from the Automatic Provider Cache Dir feature, or are better served by the Provider Cache Server due to scale or platform limitations.

What's Changed

Full Changelog: gruntwork-io/terragrunt@v0.94.0...v0.95.0

v0.94.0

Compare Source

✨ Features

  • Terraform 1.14: We are now testing Terragrunt against Terraform 1.14 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.93.13...v0.94.0

v0.93.13

Compare Source

🐛 Bug Fixes

Catalog module source URL construction

Fixed malformed version-pinned catalog module URLs where TerraformSourcePath() incorrectly placed //moduleDir after ?ref=, ensuring correct root and submodule URL formatting.

What's Changed

Full Changelog: gruntwork-io/terragrunt@v0.93.12...v0.93.13

v0.93.12

Compare Source

🐛 Bug Fixes

False positive errors during dependent units discovery

Reduced false-positive log messages emitted while discovering dependent units during destroy operations.

What's Changed

Full Changelog: gruntwork-io/terragrunt@v0.93.11...v0.93.12

v0.93.11

Compare Source

🐛 Bug Fixes

Stack files matching

Fixed stack detection so only files whose base name exactly matches the default stack name are treated as stack files.

What's Changed

Full Changelog: gruntwork-io/terragrunt@v0.93.10...v0.93.11

v0.93.10

Compare Source

🐛 Bug Fixes

Handling of disabled units in discovery

Discovery now skips units that are marked as disabled.

What's Changed

Full Changelog: gruntwork-io/terragrunt@v0.93.9...v0.93.10

v0.93.9

Compare Source

✨ New Features

Added support for Openbao encryption provider

Key provider now supports openbao

🐛 Bug Fixes

Fixed error in calling sensitive() function in HCL

HCL sensitive() function now correctly handles values and calls without errors.

What's Changed

Full Changelog: gruntwork-io/terragrunt@v0.93.8...v0.93.9

v0.93.8

Compare Source

⚙️ Process Improvements

Terragrunt static executables
  • Release pipeline now publishes statically linked executables

What's Changed

Full Changelog: gruntwork-io/terragrunt@v0.93.7...v0.93.8

v0.93.7

Compare Source

What's Changed

New Contributors

Full Changelog: gruntwork-io/terragrunt@v0.93.6...v0.93.7

v0.93.6

Compare Source

⚙️ Process Improvements

Terragrunt release automation moved to GitHub Actions

The release automation for Terragrunt has moved to GitHub Actions. With this move, Terragrunt releases now support:

  • Windows binary signing
  • Additional packaging for artifacts (.zip and .tar.gz release artifacts)

You can still download standalone executables from release assets for backward compatibility.

🧪 Experiments Updated

The filter-flag experiment now supports the source= attribute

The --filter flag can now be used to filter units by their usage of particular OpenTofu/Terraform modules in their terraform source blocks (remember that you must use the filter-flag experiment to try this).

# Filter by exact source match
terragrunt find --filter 'source=github.com/acme/foo'
terragrunt find --filter 'source=gitlab.com/example/baz'
terragrunt find --filter 'source=./module'

# Filter by source using glob patterns
terragrunt find --filter 'source=*github.com**acme/*'
terragrunt find --filter 'source=git::[email protected]:acme/**'
terragrunt find --filter 'source=**github.com**'
terragrunt find --filter 'source=gitlab.com/**'

For more information, see the filter feature documentation.

What's Changed

Full Changelog: gruntwork-io/terragrunt@v0.93.5...v0.93.6

v0.93.5

Compare Source

🧪 Experiments Updated

The filter-flag experiment now supports --filter in stack generate

The --filter flag can now be used in the stack generate command, and any command that performs stack generation, e.g. run --all (remember that you must use the filter-flag experiment to try this).

The --filter flag works in a slightly unique way when used to control stack generation in that it needs to be explicitly restricted to stacks for it to impact stack generation using the type=stack attribute filter.

e.g.

# Supported: Only generate the stacks that match the filter, as we are explicitly indicating that we are targeting stacks.
terragrunt stack generate --filter 'name=prod | type=stack'

# Not supported: This filter will be ignored, as we are not explicitly indicating that we are targeting stacks.
terragrunt stack generate --filter 'name=prod'  # This will not work

The reason for this is that stack generation can also be done automatically as part of other commands, like run, and thus we need to make it clear that we’re trying to control stack generation rather than run behavior.

# This will run any unit named 'vpc'
terragrunt run --all --filter 'vpc' -- plan

# This will run any unit named 'vpc', and prevent stack generation in any stack not named 'dev' (including any stacks named 'vpc')
terragrunt stack run --filter 'vpc' --filter 'name=dev | type=stack' -- apply

For more information, see the filter feature documentation

What's Changed

Full Changelog: gruntwork-io/terragrunt@v0.93.4...v0.93.5

v0.93.4

Compare Source

🧪 Updated Experiments

The filter-flag experiment now supports graph expressions

The --filter flag now supports usage of graph expressions, allowing users to filter based on the dependency relationship of units discovered by Terragrunt (remember that you must use the filter-flag experiment to try this).

e.g.

# Find 'service' and everything it depends on
terragrunt find --filter 'service...'

# Find 'vpc' and everything that depends on it
terragrunt find --filter '...vpc'

# Find 'db' and its complete dependency graph
terragrunt find --filter '...db...'

# Find all dependents of 'vpc' but exclude 'vpc' itself
terragrunt find --filter '...^vpc'

You can learn more about graph-based filtering in the filter feature documentation.

What's Changed

Full Changelog: gruntwork-io/terragrunt@v0.93.3...v0.93.4

v0.93.3

Compare Source

🐛 Bug Fixes

hcl validate --inputs regression on validation blocks resolved

A bug introduced in v0.93.1 preventing hcl validate --inputs from succeeding on OpenTofu/Terraform modules with variables containing validation blocks. This was caused by an error in the update to OpenTofu/Terraform .tf file parsing by Terragrunt in the hcl validate command.

That bug has been resolved.

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 becomes conflicted, 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 was generated by Mend Renovate. View the repository job log.

@renovate renovate bot added the renovate label Feb 24, 2024
@renovate renovate bot changed the title fix(deps): update github.com/davecgh/go-spew digest to 8991bc2 fix(deps): update github.com/davecgh/go-spew digest to 8991bc2 - autoclosed Feb 25, 2024
@renovate renovate bot closed this Feb 25, 2024
@renovate renovate bot deleted the renovate/github branch February 25, 2024 00:07
@renovate renovate bot changed the title fix(deps): update github.com/davecgh/go-spew digest to 8991bc2 - autoclosed fix(deps): update github.com/davecgh/go-spew digest to 8991bc2 Feb 27, 2024
@renovate renovate bot reopened this Feb 27, 2024
@renovate renovate bot restored the renovate/github branch February 27, 2024 06:20
@renovate renovate bot force-pushed the renovate/github branch from 70d1ddc to 471e261 Compare February 27, 2024 06:21
@renovate renovate bot changed the title fix(deps): update github.com/davecgh/go-spew digest to 8991bc2 fix(deps): update github.com/davecgh/go-spew digest to 8991bc2 - autoclosed Feb 27, 2024
@renovate renovate bot closed this Feb 27, 2024
@renovate renovate bot deleted the renovate/github branch February 27, 2024 10:18
@renovate renovate bot changed the title fix(deps): update github.com/davecgh/go-spew digest to 8991bc2 - autoclosed fix(deps): update github.com/davecgh/go-spew digest to 8991bc2 Feb 29, 2024
@renovate renovate bot reopened this Feb 29, 2024
@renovate renovate bot restored the renovate/github branch February 29, 2024 22:29
@renovate renovate bot changed the title fix(deps): update github.com/davecgh/go-spew digest to 8991bc2 fix(deps): update module github.com/hashicorp/hcl/v2 to v2.20.0 Feb 29, 2024
@renovate renovate bot force-pushed the renovate/github branch from 471e261 to d110f36 Compare February 29, 2024 22:30
@renovate renovate bot changed the title fix(deps): update module github.com/hashicorp/hcl/v2 to v2.20.0 fix(deps): update github Mar 19, 2024
@renovate renovate bot changed the title fix(deps): update github fix(deps): update module github.com/hashicorp/hcl/v2 to v2.20.0 Mar 19, 2024
@renovate renovate bot changed the title fix(deps): update module github.com/hashicorp/hcl/v2 to v2.20.0 fix(deps): update github Mar 21, 2024
@renovate renovate bot changed the title fix(deps): update github fix(deps): update module github.com/hashicorp/hcl/v2 to v2.20.0 Mar 21, 2024
@renovate renovate bot changed the title fix(deps): update module github.com/hashicorp/hcl/v2 to v2.20.0 fix(deps): update module github.com/hashicorp/hcl/v2 to v2.20.1 Mar 26, 2024
@renovate renovate bot force-pushed the renovate/github branch from d110f36 to c1ba913 Compare March 26, 2024 19:49
@renovate renovate bot changed the title fix(deps): update module github.com/hashicorp/hcl/v2 to v2.20.1 fix(deps): update github Mar 27, 2024
@renovate renovate bot changed the title fix(deps): update github fix(deps): update module github.com/hashicorp/hcl/v2 to v2.20.1 Mar 27, 2024
@renovate renovate bot force-pushed the renovate/github branch from c1ba913 to 1de6418 Compare April 4, 2024 19:24
@renovate renovate bot changed the title fix(deps): update module github.com/hashicorp/hcl/v2 to v2.20.1 fix(deps): update github (minor) Apr 4, 2024
@renovate renovate bot changed the title fix(deps): update github (minor) fix(deps): update github Apr 6, 2024
@renovate renovate bot changed the title fix(deps): update github fix(deps): update github (minor) Apr 6, 2024
@renovate renovate bot force-pushed the renovate/github branch 2 times, most recently from db79e7c to c21d008 Compare April 10, 2024 17:56
@renovate renovate bot force-pushed the renovate/github branch 2 times, most recently from cd72d57 to e67f0f6 Compare November 1, 2025 00:55
@renovate renovate bot force-pushed the renovate/github branch 6 times, most recently from 551541d to 5740ebe Compare November 10, 2025 22:37
@renovate renovate bot force-pushed the renovate/github branch 5 times, most recently from 48c8ddf to 7fed5fa Compare November 18, 2025 05:08
@renovate renovate bot force-pushed the renovate/github branch 4 times, most recently from 42bba10 to 6eb5a3f Compare November 24, 2025 18:55
@renovate renovate bot force-pushed the renovate/github branch 3 times, most recently from 8f6c4d3 to 3b30463 Compare December 5, 2025 22:06
@renovate renovate bot force-pushed the renovate/github branch 5 times, most recently from d2a1357 to 3f35ab0 Compare December 15, 2025 19:06
@renovate renovate bot force-pushed the renovate/github branch 2 times, most recently from 42b0f25 to f95a280 Compare December 23, 2025 14:44
@renovate
Copy link
Contributor Author

renovate bot commented Dec 23, 2025 •
edited
Loading

ℹ️ Artifact update notice

File name: go.mod

In order to perform the update(s) described in the table above, Renovate ran the go get command, which resulted in the following additional change(s):

  • 103 additional dependencies were updated
  • The go directive was updated for compatibility reasons

Details:

Package Change
go 1.24.1 -> 1.25
golang.org/x/exp v0.0.0-20250106191152-7588d65b2ba8 -> v0.0.0-20251017212417-90e834f514db
golang.org/x/term v0.30.0 -> v0.38.0
cel.dev/expr v0.22.0 -> v0.25.1
cloud.google.com/go v0.120.0 -> v0.123.0
cloud.google.com/go/auth v0.15.0 -> v0.17.0
cloud.google.com/go/compute/metadata v0.6.0 -> v0.9.0
cloud.google.com/go/iam v1.4.2 -> v1.5.3
cloud.google.com/go/kms v1.21.0 -> v1.23.2
cloud.google.com/go/longrunning v0.6.5 -> v0.7.0
cloud.google.com/go/monitoring v1.24.1 -> v1.24.3
cloud.google.com/go/storage v1.51.0 -> v1.58.0
dario.cat/mergo v1.0.1 -> v1.0.2
github.com/Azure/azure-sdk-for-go/sdk/azcore v1.17.0 -> v1.19.1
github.com/Azure/azure-sdk-for-go/sdk/azidentity v1.8.1 -> v1.13.0
github.com/Azure/azure-sdk-for-go/sdk/internal v1.10.0 -> v1.11.2
github.com/Azure/azure-sdk-for-go/sdk/security/keyvault/azkeys v1.3.0 -> v1.4.0
github.com/Azure/azure-sdk-for-go/sdk/security/keyvault/internal v1.1.0 -> v1.2.0
github.com/AzureAD/microsoft-authentication-library-for-go v1.3.3 -> v1.5.0
github.com/GoogleCloudPlatform/opentelemetry-operations-go/detectors/gcp v1.27.0 -> v1.30.0
github.com/GoogleCloudPlatform/opentelemetry-operations-go/exporter/metric v0.51.0 -> v0.54.0
github.com/GoogleCloudPlatform/opentelemetry-operations-go/internal/resourcemapping v0.51.0 -> v0.54.0
github.com/ProtonMail/go-crypto v1.1.6 -> v1.3.0
github.com/aws/aws-sdk-go-v2 v1.36.3 -> v1.41.0
github.com/aws/aws-sdk-go-v2/aws/protocol/eventstream v1.6.10 -> v1.7.4
github.com/aws/aws-sdk-go-v2/config v1.29.6 -> v1.32.6
github.com/aws/aws-sdk-go-v2/credentials v1.17.59 -> v1.19.6
github.com/aws/aws-sdk-go-v2/feature/ec2/imds v1.16.28 -> v1.18.16
github.com/aws/aws-sdk-go-v2/feature/s3/manager v1.17.53 -> v1.19.9
github.com/aws/aws-sdk-go-v2/internal/configsources v1.3.34 -> v1.4.16
github.com/aws/aws-sdk-go-v2/internal/endpoints/v2 v2.6.34 -> v2.7.16
github.com/aws/aws-sdk-go-v2/internal/ini v1.8.2 -> v1.8.4
github.com/aws/aws-sdk-go-v2/internal/v4a v1.3.34 -> v1.4.16
github.com/aws/aws-sdk-go-v2/service/internal/accept-encoding v1.12.3 -> v1.13.4
github.com/aws/aws-sdk-go-v2/service/internal/checksum v1.7.0 -> v1.9.7
github.com/aws/aws-sdk-go-v2/service/internal/presigned-url v1.12.15 -> v1.13.16
github.com/aws/aws-sdk-go-v2/service/internal/s3shared v1.18.15 -> v1.19.16
github.com/aws/aws-sdk-go-v2/service/kms v1.37.18 -> v1.45.6
github.com/aws/aws-sdk-go-v2/service/s3 v1.78.2 -> v1.95.0
github.com/cloudflare/circl v1.6.0 -> v1.6.1
github.com/cncf/xds/go v0.0.0-20250121191232-2f005788dc42 -> v0.0.0-20251110193048-8bfbf64dc13e
github.com/cpuguy83/go-md2man/v2 v2.0.6 -> v2.0.7
github.com/envoyproxy/go-control-plane/envoy v1.32.4 -> v1.36.0
github.com/fsnotify/fsnotify v1.7.0 -> v1.9.0
github.com/getsops/sops/v3 v3.9.4 -> v3.11.0
github.com/go-jose/go-jose/v4 v4.0.5 -> v4.1.3
github.com/go-logr/logr v1.4.2 -> v1.4.3
github.com/googleapis/enterprise-certificate-proxy v0.3.6 -> v0.3.7
github.com/googleapis/gax-go/v2 v2.14.1 -> v2.15.0
github.com/grpc-ecosystem/grpc-gateway/v2 v2.26.3 -> v2.27.4
github.com/gruntwork-io/terragrunt-engine-go v0.0.13 -> v0.0.16
github.com/hashicorp/go-getter v1.7.8 -> v1.8.3
github.com/hashicorp/go-plugin v1.6.3 -> v1.7.0
github.com/hashicorp/go-retryablehttp v0.7.7 -> v0.7.8
github.com/hashicorp/go-secure-stdlib/parseutil v0.1.9 -> v0.2.0
github.com/hashicorp/go-version v1.7.0 -> v1.8.0
github.com/hashicorp/vault/api v1.15.0 -> v1.22.0
github.com/huandu/go-clone v1.7.2 -> v1.7.3
github.com/klauspost/compress v1.17.11 -> v1.18.1
github.com/magiconair/properties v1.8.7 -> v1.8.10
github.com/mattn/go-runewidth v0.0.16 -> v0.0.19
github.com/oklog/run v1.1.0 -> v1.2.0
github.com/pelletier/go-toml/v2 v2.2.2 -> v2.2.4
github.com/sagikazarmark/locafero v0.4.0 -> v0.11.0
github.com/sourcegraph/conc v0.3.0 -> v0.3.1-0.20240121214520-5f936abd7ae8
github.com/spf13/afero v1.12.0 -> v1.15.0
github.com/spf13/cast v1.7.1 -> v1.10.0
github.com/spf13/pflag v1.0.5 -> v1.0.10
github.com/ulikunitz/xz v0.5.12 -> v0.5.15
github.com/urfave/cli v1.22.16 -> v1.22.17
github.com/urfave/cli/v2 v2.27.6 -> v2.27.7
github.com/xrash/smetrics v0.0.0-20240521201337-686a1a2994c1 -> v0.0.0-20250705151800-55b8f293f342
go.opentelemetry.io/auto/sdk v1.1.0 -> v1.2.1
go.opentelemetry.io/contrib/detectors/gcp v1.35.0 -> v1.38.0
go.opentelemetry.io/contrib/instrumentation/google.golang.org/grpc/otelgrpc v0.60.0 -> v0.63.0
go.opentelemetry.io/contrib/instrumentation/net/http/otelhttp v0.60.0 -> v0.63.0
go.opentelemetry.io/otel v1.35.0 -> v1.39.0
go.opentelemetry.io/otel/exporters/otlp/otlpmetric/otlpmetricgrpc v1.35.0 -> v1.39.0
go.opentelemetry.io/otel/exporters/otlp/otlpmetric/otlpmetrichttp v1.35.0 -> v1.38.0
go.opentelemetry.io/otel/exporters/otlp/otlptrace v1.35.0 -> v1.39.0
go.opentelemetry.io/otel/exporters/otlp/otlptrace/otlptracegrpc v1.35.0 -> v1.39.0
go.opentelemetry.io/otel/exporters/otlp/otlptrace/otlptracehttp v1.35.0 -> v1.39.0
go.opentelemetry.io/otel/exporters/stdout/stdoutmetric v1.35.0 -> v1.39.0
go.opentelemetry.io/otel/exporters/stdout/stdouttrace v1.34.0 -> v1.39.0
go.opentelemetry.io/otel/metric v1.35.0 -> v1.39.0
go.opentelemetry.io/otel/sdk v1.35.0 -> v1.39.0
go.opentelemetry.io/otel/sdk/metric v1.35.0 -> v1.39.0
go.opentelemetry.io/otel/trace v1.35.0 -> v1.39.0
go.opentelemetry.io/proto/otlp v1.5.0 -> v1.9.0
golang.org/x/crypto v0.36.0 -> v0.46.0
golang.org/x/mod v0.24.0 -> v0.30.0
golang.org/x/net v0.38.0 -> v0.48.0
golang.org/x/oauth2 v0.28.0 -> v0.34.0
golang.org/x/sync v0.12.0 -> v0.19.0
golang.org/x/sys v0.31.0 -> v0.39.0
golang.org/x/text v0.23.0 -> v0.32.0
golang.org/x/time v0.11.0 -> v0.14.0
golang.org/x/tools v0.29.0 -> v0.39.0
google.golang.org/api v0.227.0 -> v0.256.0
google.golang.org/genproto v0.0.0-20250313205543-e70fdf4c4cb4 -> v0.0.0-20251111163417-95abcf5c77ba
google.golang.org/genproto/googleapis/api v0.0.0-20250313205543-e70fdf4c4cb4 -> v0.0.0-20251222181119-0a764e51fe1b
google.golang.org/genproto/googleapis/rpc v0.0.0-20250313205543-e70fdf4c4cb4 -> v0.0.0-20251222181119-0a764e51fe1b
google.golang.org/grpc v1.71.0 -> v1.78.0
google.golang.org/protobuf v1.36.6 -> v1.36.11

@renovate renovate bot force-pushed the renovate/github branch from f95a280 to 44129be Compare January 5, 2026 19:27
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

renovate

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

1 participant