chore(deps): update dependency terragrunt to v1#1595
Merged
Conversation
f5136b1 to
4a96460
Compare
Terraform PlanShared✅ |
4a96460 to
0d8733b
Compare
0d8733b to
b0d530f
Compare
jrasm91
approved these changes
May 13, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
0.99.5→1.0.4Release Notes
gruntwork-io/terragrunt (terragrunt)
v1.0.4Compare Source
🏎️ Performance Improvements
run_cmdand Git repo-root results memoized without the Provider Cache ServerWithin a single command, repeated
run_cmd(...)calls and repeated Git repo-root lookups across units used to share their cached results only when the Provider Cache Server was running. Commands invoked without--provider-cache(the common case forfind,list, andrun --allagainst estates that do not need provider caching) re-evaluated eachrun_cmdand re-shelled togit rev-parse --show-toplevelfor every unit.Both caches are now active for every command, so identical
run_cmdarguments and repeated repo-root lookups are reused across units regardless of whether the Provider Cache Server is enabled.fast-copystrict controlWith the new
fast-copystrict control enabled, Terragrunt compiles eachinclude_in_copyandexclude_from_copypattern once and evaluates it inline during a single copy walk. This avoids re-walking subdirectories for every pattern, which should result in noticeable speed improvements for large source modules.The new matcher does not collapse
**to zero path segments when a neighbor is a wildcard, soa/**/*.tfmatchesa/sub/main.tfbut nota/main.tf. Patterns that relied on the old collapsing behavior should use brace alternation like{*.tf,**/*.tf}to cover both depths.Fewer
git rev-parseinvocations on large estatesThe
get_repo_root()HCL function, the runner, and thefindandlistdiscovery commands all ask Git for the enclosing repository root. Previously, two units in the same repository each triggered their owngit rev-parse --show-toplevel, even when the answer was identical. On large estates this added up to one fork per unit (and sometimes more) for a value that never changed.A repository discovered for one working directory is now reused for any other working directory inside it, for the duration of the command. Nested repositories (a checkout vendored inside another) still resolve to their own root.
🐛 Bug Fixes
--auth-provider-cmdno longer runs once per dependency cache directoryResolving
dependencyoutputs ran the configured--auth-provider-cmdagain from inside each.terragrunt-cacheworking directory, on top of the call already made for the unit.Terragrunt now reuses the credentials already obtained for the dependency when reading outputs from a cached working directory, so
--auth-provider-cmdis invoked once per dependency instead of twice.Fixed
excludeblock being dropped when defined only in an included parentA unit that pulled in an
excludeblock from an include that did not declare its ownexcludeblock saw the include'sexcludeconfigurations ignored.Included
excludeblocks now get properly merged into unit configurations.Reported in #5089. Thanks to @HeikoNeblung for contributing this fix!
Fixed
terragrunt find --includefailing on relative include pathsRunning
terragrunt find --includeagainst units whoseincludeblocks reference parent configs with relative paths (../root.hcl,./common.hcl, bare filenames, etc.) emitted errors likeRel: can't make ../root.hcl relative to /abs/working-dirand dropped those entries from the output.Relative include paths are now resolved against the unit's directory before being made relative to the working directory, matching how the rest of Terragrunt interprets the
pathattribute on anincludeblock.findandlistno longer hard-fail when a path cannot be made relative to its base. The condition is logged as a warning and the path is emitted as-is, so output stays complete and the command exits zero.Tolerate non-JSON warnings in
tofu/terraform output -jsonResolving
dependencyoutputs no longer fails when the underlyingtofu/terraform output -jsoninvocation prints a deprecation warning to stdout alongside the JSON payload. Terraform 1.15.0 introduced a backend deprecation warning for the S3dynamodb_tableparameter that is emitted on stdout after the JSON object, which broke parsing with errors likeinvalid character 'W' after top-level valueand the misleading downstream messageThere is no variable named "dependency".Terragrunt now isolates the first JSON object in the captured stdout, so leading log lines (for example, the long-standing AWS Client Side Monitoring
Enabling CSMline) and trailing warning blocks are both ignored when reading dependency outputs.Resolves #6001. Thanks to @jpke for contributing this fix!
get_repo_root()returns OS-native separators on Windowsgit rev-parse --show-toplevelalways emits forward-slash paths, even on Windows. Terragrunt returned that string unchanged fromget_repo_root(), so configurations that compared the result againstpath/filepath-style paths or fed it back into helpers expecting OS-native separators saw spurious mismatches and broken joins on Windows.The output is now normalized to OS-native separators before being returned, so
get_repo_root()producesC:\repo\pathon Windows and/repo/pathon Linux and macOS.Reported in #5976.
Hardened module manifest handling
Terragrunt now bounds
.terragrunt-module-manifestcleanup to the manifest's own folder, skips paths with symlinked parents, and removes invalid manifests after reading any valid entries. Existing manifests keep the same gob format.Provider Cache Server now supports custom
hostblocksRunning
terragruntwith the Provider Cache Server enabled against a private registry declared via ahostblock in.terraformrc(or a file referenced byTF_CLI_CONFIG_FILE) failed with errors such asprovider registry.opentofu.org/<org>/<provider> was not found, because the cache server proxy did not recognize the custom registry and rewrote requests toregistry.opentofu.org.Terragrunt now registers each custom
hostblock with the cache server, seeds its service discovery from theservicesmap so registries that do not serve.well-known/terraform.jsonstill work, and forwardsOPENTOFU_NETRC_*/TF_TOKEN_*credentials so authenticated registries continue to authenticate through the proxy.Resolves #5916. Thanks to @elkh510 for contributing this fix!
🧪 Experiments Updated
stack-dependencies— Stricter validation and clearer parse errors forautoincludeMalformed configuration inside an
autoincludeblock previously produced misleading messages or, in some cases, was silently ignored during stack discovery.Two changes tighten this up:
dependencyblock insideautoincludemust declare exactly one label. Zero labels (dependency {}) and multiple labels (dependency "a" "b" {}) are now rejected at parse time with a diagnostic that points at the offending block.autoincludefiles duringstack generate,find, andlistare surfaced with the underlying HCL diagnostic instead of being swallowed or remapped to a generic discovery error.Reported in #5980.
cas— Local paths supported as stack component sourcesCAS-backed stack generation now accepts a local filesystem path as the
sourceof a consumerstackorunitblock, in addition to a remote Git URL. Terragrunt copies the referenced directory into a temporary directory, computes a content-addressed root hash over the copy, and applies the sameupdate_source_with_casrewriting as the remote flow. The original directory is left untouched.This makes a catalog usable against a local checkout under the same
update_source_with_cas = trueattributes that already work for Git URLs, which is helpful when iterating on a catalog before tagging a release.See the CAS documentation and Explicit Stacks: Local catalog sources for details.
catalog-redesign— Units and stacks, scaffolded values, and key-binding cleanupThe redesigned
terragrunt catalogTUI gains two new component kinds, a guided scaffolding flow for placing them, and a small key-binding cleanup.Units and stacks join modules and templates
Catalog discovery now classifies units (directories containing a
terragrunt.hcl) and stacks (directories containing aterragrunt.stack.hcl) as first-class component kinds, alongside OpenTofu/Terraform modules and boilerplate templates. The list view picks them up automatically and they appear under their own tabs; presstabandshift+tabto cycle.When more than one classification could apply to the same directory (for example, a stack directory that also contains a unit), Terragrunt resolves it to a single kind under a fixed precedence: template, stack, unit, module.
Copy and scaffolded values
Selecting a unit or stack from the catalog now offers a copy action that materializes the component into your working directory. Terragrunt walks the copied component for
values.<name>references and, if it finds any, writes a siblingterragrunt.values.hclstub. Names referenced outside atry(...)are listed as required with a"TODO"placeholder; names referenced through atry(...)are listed as optional, pre-populated with the literal default from the fallback. An existingterragrunt.values.hclis left alone.After the TUI exits, Terragrunt prints a short callout pointing at the directory it wrote to and any follow-up command you need to run, instead of leaving you to find the new directory yourself.
Catalog key bindings
The
ctrl+jbinding on the catalog list has been removed in favor ofenteralone for choosing a focused entry, and dropped from the navigation set used while filtering. The mini help footer is updated to match.stack-dependencies- Separate filenames for unit vs stack autoincludesGenerated autoinclude files now use distinct filenames depending on the component kind, so tooling (LSP,
read_terragrunt_config(), indexers) can identify a file's purpose from its name alone:terragrunt.autoinclude.hcl.stack { ... }) are now written asterragrunt.autoinclude.stack.hcl. The.stack.hclsuffix mirrorsterragrunt.stack.hcl, matching the convention used elsewhere for stack files.This change implements the naming convention proposed in the Stack Dependencies RFC so configurations for units and stacks always live in files whose names clearly indicate their purpose.
To learn more, see the experiment documentation.
stack-dependencies— Nested stack paths and discovery integrationThe
stack-dependenciesexperiment gains two improvements: nested stack path references at arbitrary depth, and integration with thefindandlistdiscovery commands.Nested stack path references
stack.<name>.<nested_stack>.pathnow resolves at arbitrary nesting depth. Previously, only units within a stack were reachable viastack.<name>.<unit_name>.path; nested stacks are now first-class references too.Discovery commands surface stack dependencies
The
terragrunt findandterragrunt listdiscovery commands now reflect stack dependencies generated by theautoincludeblock. The DAG output correctly orders units by their autoinclude dependencies and shows dependency relationships in JSON, tree, and long formats.Multi-level dependency trees (for example,
A → B,CwhereB → D,E) are ordered correctly in DAG mode: leaf units appear first, parents appear after all their dependencies.To learn more, see the experiment documentation.
Cache and plugin directories follow platform conventions
Terragrunt's global cache directory now resolves to the platform's user cache location instead of a hard-coded
~/.cache/terragrunt. On Linux this honorsXDG_CACHE_HOME(still~/.cache/terragruntby default), on macOS it resolves to~/Library/Caches/terragrunt, and on Windows it resolves under%LocalAppData%. The CAS content store, the auto provider cache, and the IaC engine plugin directory all move with it.Existing caches at the previous locations are not migrated. They become orphaned and continue to consume disk space until removed.
Consider deleting the old paths to reclaim that space if you are on macOS or Windows, or have configured a custom
XDG_CACHE_HOME:What's Changed
--auth-provider-cmdcall by @yhakbar in #6045FromSlashon return ofgit rev-parse --show-toplevelby @yhakbar in #5987ctrl-\+jin the catalog key bindings by @yhakbar in #6007get_repo_root()better by @yhakbar in #5989Pull Requestssection to the changelog by @yhakbar in #5982v1.0.4by @yhakbar in #6005v1.0.4by @yhakbar in #6050fast-copystrict control by @yhakbar in #5966lllcoverage toworktreesby @yhakbar in #5861lllcoverage toos-execby @yhakbar in #5862lllcoverage torunner-credsby @yhakbar in #5865lllcoverage totflintby @yhakbar in #5866lllcoverage toqueueby @yhakbar in #5867vexecinto engine by @yhakbar in #5957vexecintoCommandby @yhakbar in #6004New Contributors
Full Changelog: gruntwork-io/terragrunt@v1.0.3...v1.0.4
v1.0.3Compare Source
✨ New Features
--no-casflag for disabling CAS per commandThe new
--no-casflag disables the CAS for a single invocation, even when thecasexperiment is enabled. It is available onrun,stack generate, andstack run.This is useful when you want to fall back to the standard getter path without unwinding experiment configuration.
Generation and runs error when
--no-casis combined withupdate_source_with_cas = trueon any reachableunit,stack, orterraformblock, since relative sources in catalog repositories cannot be resolved without the CAS.🐛 Bug Fixes
hcl fmt --diffno longer requires thediffbinaryPreviously,
terragrunt hcl fmt --diffspawned adiffprocess discovered in$PATHto render its output. This made it incompatible with minimal container images and Windows installations where that binary was unavailable.The flag now produces unified diff output without depending on any external binary.
Note that the output is not byte-identical to GNU
diff -u. Each file diff is now preceded by adiff old/<path> new/<path>header line, and the---/+++lines no longer include a trailing timestamp. Scripts that parsed the previous output may need small adjustments.Fixed crash when
includeandlocalswithread_terragrunt_configcoexistA unit that combined an
includeblock with alocalsblock callingread_terragrunt_config(...)could crash during discovery, surfacing as a misleadingCall to function "read_terragrunt_config" failederror pointed at thelocalsexpression.Discovery now reports the underlying error instead of crashing.
Reported in #5949.
Fixed crash when a
root.hcldeclares noremote_stateblockA
root.hclthat only declaredlocals(or otherwise omitted aremote_stateblock) could trigger a nil pointer dereference inside Terragrunt's remote-state initialization. Downstream tools that embed the Terragrunt config parser, such asterragrunt-ls, crashed on every such file.A missing
remote_stateblock now initializes an empty remote-state value instead of panicking, so parsing proceeds normally when no backend is configured.Reported in terragrunt-ls#134.
Thanks to @SAY-5 for contributing this fix!
Fixed a race condition in
terragrunt stack generateFixed a race condition in
terragrunt stack generatethat could produce non-deterministic file errors on nested stack hierarchies. The same stack file could reach the worker pool twice through different path forms and cause the duplicate writes to conflict with each other. Paths are now normalized before dispatch so each stack file is generated exactly once per invocation.When a stack file is legitimately claimed by more than one parent during generation, Terragrunt now logs a warning that names the contending parents and records the latest claimant, so the configuration can be corrected before it causes silent overwrites.
Fixed data race in
--versionflag parsing under concurrent CLI invocationsWhen multiple Terragrunt CLI invocations ran concurrently in the same process, urfave/cli/v2's package-level
VersionFlagsingleton was mutated concurrently by each invocation's flag-parsing path, producing aWARNING: DATA RACEon shared flag state.Terragrunt now sets
cli.App.HideVersion = trueat construction, which prevents urfave from auto-appending its sharedVersionFlaginto each App's flag set. The--version/-vflag is unchanged from the user's perspective — it is handled by Terragrunt's own flag registered ininternal/cli/flags/global.NewHelpVersionFlags.🧪 Experiments Added
mark-many-as-read— Mark many files as read in one stepEnable the new
mark-many-as-readexperiment to turn on two behaviors that each mark many files as read in a single call: automatic marking of files inside a localterraform { source = "..." }block, and the newmark_glob_as_readHCL function.With the experiment on, a unit like this:
records every
*.tf,*.tf.json,*.hcl,*.tofu, and*.tofu.jsonfile found under../../modules/service(recursively) as read for the unit. Non-source files such asREADME.mdare skipped. A reading-based filter expression such as--filter 'reading=../../modules/service/**'then matches every unit that points at the module, so a change to any file in the module cascades to its consumers.The same experiment also enables a new HCL function,
mark_glob_as_read(pattern), which expands a glob using the samegobwas/globsyntax as filter expressions and marks every matching file as read. It returns the list of absolute paths that matched, so it composes with other expressions:**only collapses the surrounding separators when the adjacent segments are literals, so match-at-any-depth with a wildcard trailing segment is written as{*.yaml,**/*.yaml}. See the HCL reference for full pattern syntax.This is useful when a unit reads a collection of files indirectly (for example, via
run_cmdortemplatefile) and you want changes to any of them to trigger the unit through reading-based filters. Callingmark_glob_as_readwithout the experiment enabled returns an error.🧪 Experiments Updated
cas— Stack integration viaupdate_source_with_casThe
casexperiment now integrates with stacks. Units andterraformblocks can setupdate_source_with_cas = trueto use relativesourcepaths in catalog repositories, removing the need to plumb remote Git URLs throughvaluesexpressions.During stack generation, Terragrunt rewrites these relative sources to
cas::references that resolve against content stored in the CAS. The repository is cloned once, and subsequent stack generations resolve content from the local store without network access. Generated.terragrunt-stackfiles contain deterministic CAS references, so regeneration does not produce spurious diffs.CAS also supports SHA-256 repositories now, detected automatically via
git rev-parse --show-object-format. The on-disk store layout was reorganized intoblobs/andtrees/namespaces under~/.cache/terragrunt/cas/store/.To learn more, see the CAS documentation and Explicit Stacks: CAS Integration.
catalog-redesign— Templates and.terragrunt-catalog-ignoreThe
catalog-redesignexperiment picked up user-visible improvements to discovery and filtering.Discovery walks the entire repository instead of only a
modules/directory, so modules and templates can live anywhere in the tree. Boilerplate templates (directories containing a.boilerplate/subdirectory or a top-levelboilerplate.yml) are discovered as a distinct component kind alongside OpenTofu/Terraform modules and labeled as templates in the UI. When a directory qualifies as both, it is classified as a template.Catalog authors can commit a
.terragrunt-catalog-ignorefile at the repo root to keep directories such asexamples/ortest/out of discovery. The file uses.gitignore-style semantics: one pattern per line,#for comments,!for negation, and last match wins. Matching is anchored at the repo root; a lone*does not cross/, and**does.An
--ignore-fileflag (also available viaTG_IGNORE_FILE) points at an additional ignore file that is layered on top of the repo's.terragrunt-catalog-ignore. The extra rules are appended under last-match-wins semantics, so the flag can either add new exclusions or re-include paths that the repo file excluded.To learn more, see Excluding paths from discovery.
The list view is split into
All,Modules, andTemplatestabs, withAllselected on launch so every discovered component is visible without switching views. Presstabandshift+tabto cycle between them; each tab keeps its own cursor and search filter.stack-dependencies— Multi-level nestedstack.<name>.<nested_stack>.pathreferencesThe
stack-dependenciesexperiment already supportedstack.<name>.path(a whole stack) andstack.<name>.<unit_name>.path(a unit inside a stack). It now also resolves references where the second segment is itself a nested stack, so anautoincludeblock in a parent stack can target a stack that lives inside another stack:Here
stack.infra.deep.pathresolves to the generated directory of astack "deep"block declared insidecatalog/stacks/infra/terragrunt.stack.hcl. This makes deeper stack hierarchies addressable from a single dependency expression without flattening the layout.What's Changed
read_terragrunt_config()by @yhakbar in #5953v1.0.3by @yhakbar in #5977catalog-redesignby @yhakbar in #5940vexecintoNewGitRunnerby @yhakbar in #5934lllcoverage toamazonstsby @yhakbar in #5852lllcoverage torunner-commonby @yhakbar in #5853lllcoverage torunner-graphby @yhakbar in #5854lllcoverage tolistby @yhakbar in #5855lllcoverage toerrorconfigby @yhakbar in #5856lllcoverage toexperimentby @yhakbar in #5857lllcoverage toexternalcmdby @yhakbar in #5858lllcoverage tocache-controllersby @yhakbar in #5859lllcoverage tovfsby @yhakbar in #5860lllcoverage tostackby @yhakbar in #5841lllcoverage tobackend-deleteby @yhakbar in #5842lllcoverage toclonerby @yhakbar in #5843lllcoverage toengineby @yhakbar in #5844lllcoverage togitby @yhakbar in #5845vexecby @yhakbar in #5935lllcoverage toprepareby @yhakbar in #5846lllcoverage toexecby @yhakbar in #5847lllcoverage tofindby @yhakbar in #5848lllcoverage tostacks-outputby @yhakbar in #5850lllcoverage toplaceholdersby @yhakbar in #5851diffby @yhakbar in #5954New Contributors
Full Changelog: gruntwork-io/terragrunt@v1.0.2...v1.0.3
v1.0.2Compare Source
🐛 Bug Fixes
shared_credentials_filesand other list/map backend config values were serialized incorrectlySetting
shared_credentials_files(or any other list-valued key) in theremote_state.configblock produced a broken-backend-configargument:OpenTofu and Terraform both failed to parse this. The same problem affected map-valued keys. Lists and maps are now written as single-line HCL (
["/a/creds","/b/creds"]and{key="value"}), and strings inside them are quoted so embedded quotes, newlines, and tabs survive the round trip.Thanks to @Rahul-Kumar-prog for contributing this fix!
Panic in
get_repo_root()when OpenTelemetry tracing is enabled with TRACEPARENTRunning
terragrunt stack generate(or any command that invoked shell commands likegit rev-parse) with OpenTelemetry trace exporting enabled (TG_TELEMETRY_TRACE_EXPORTER=http) caused a nil pointer panic:The root cause of the panic was fixed, and telemetry codepaths have been hardened against future panics.
stack outputnow respects theexcludeblockterragrunt stack outputpreviously ignored theexcludeblock on units, attempting to fetch outputs (including directly from S3 state when using--dependency-fetch-output-from-state) for units that should have been excluded.The fix uses Terragrunt discovery to identify excluded units before reading outputs. Excluded units are now omitted from the stack output entirely, consistent with how they are handled during
stack run.To exclude a unit from
stack output, add"output"to theactionslist in theexcludeblock:Special action values
"all"and"all_except_output"are also supported.🧪 Experiments Added
catalog-redesign— Reworkedterragrunt catalogTUIA new
catalog-redesignexperiment reworks the design of theterragrunt catalogTUI.terragrunt catalognow launches the TUI right away and runs discovery in the background instead of waiting for discovery to complete before launching the TUI. As a consequence,terragrunt catalogusers with large catalogs should see significant speed improvements as they launch theterragrunt catalogTUI.Modules now stream into the list view of the catalog as they are discovered, so you'll be able to select and use a module even if your entire catalog hasn't been discovered yet.
If
catalog.urlsis not configured inroot.hcl,terragrunt catalogno longer errors. A welcome screen explains how to populate the catalog and can open the catalog documentation on a keypress. In addition,terraform.sourcevalues from existing units are automatically included in the set of URLs used for discovery, so users with existing units get a populated catalog pointing to other modules that can be pulled from the same module source without any additional configuration.This experiment is subject to change, and core elements of the design are being iterated on rapidly.
To try it out, run:
To learn more, see the experiment documentation.
🧪 Experiments Updated
stack-dependencies— Cross-stack dependency support and autoinclude improvementsThe
stack-dependenciesexperiment now supports cross-stack and nested-stack dependency patterns, expanding theautoincludeblock capabilities interragrunt.stack.hclfiles.New features:
stack.<name>.pathreferences for depending on an entire stack. The DAG expands the stack into its constituent units so that all units in the stack complete before the dependent unit runsstack.<name>.<unit_name>.pathreferences for depending on a specific unit within a nested stack (fine-grained cross-stack dependencies)dependencyblocks targeting stack directories — aggregated outputs from all units in the stack are accessible asdependency.stack_name.outputs.unit_name.output_keylocal.*in autoinclude — expressions mixinglocal.*anddependency.*are partially evaluated during stack generation: locals resolve to literals while dependency references are preserved for evaluation when the unit is appliedDependency on an entire stack:
Dependency on a unit within a nested stack:
To learn more, see the experiment documentation.
⚙️ Process Updates
Install script now supports tip and test builds
The install script can now install tip builds and on-demand test builds. Three new flags are available:
--tipinstalls the latest tip build frommain--testinstalls an on-demand test build--commit <sha>installs a build for a specific commitDownloads are verified against GPG/Cosign signatures and SHA256 checksums before installation.
Tip build notifications on referenced issues
When a tip build is produced on
mainfor a merged PR, Terragrunt now posts a comment on any issues that PR references, linking to the build and including instructions for installing and testing it.What's Changed
catalog-redesignexperiment by @yhakbar in #5894httptestin./internal/tfto avoid issues from integration in unit tests by @yhakbar in #5925v1.0.2changelog entries by @yhakbar in #5927vexecby @yhakbar in #5931vfsincasby @yhakbar in #5908lllcoverage toconfigbridgeby @yhakbar in #5834lllcoverage toerrorsby @yhakbar in #5833lllcoverage togcphelperby @yhakbar in #5832lllcoverage togenerateby @yhakbar in #5840lllcoverage tohelpby @yhakbar in #5835lllcoverage tomiddlewareby @yhakbar in #5839lllcoverage totipsby @yhakbar in #5837lllcoverage totuiby @yhakbar in #5836lllcoverage towriterby @yhakbar in #5838Configuration
📅 Schedule: (UTC)
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.