Gruntwork docs v2.4.48 - Cost controls and hook diagnostics
Gruntwork docs v2.4.48, published on October 6, 2026, adds documentation for the Gruntwork provided Infracost hook and its warn and deny cost thresholds. These are the changes I would read first when reviewing cost checks in a pipeline. GitHub marks this documentation release as a regular release, with no prerelease flag.
The full release notes are on the GitHub release page.
Infracost hook and cost thresholds
The release adds documentation for the Gruntwork provided Infracost hook. A separate change documents warn and deny cost thresholds, putting the cost check and its threshold settings among the main additions to this version.
For an operator, those are two related parts of the setup to understand: the hook itself and the thresholds used for warnings or denials. The release notes name both, but do not include configuration examples or threshold values. The linked documentation changes are the place to inspect those details before translating a team’s cost policy into configuration.
Hook errors get documentation
The maintainers also document hook error outputs. That gives readers a specific reference change to follow when investigating a failed hook.
This entry describes documentation work. It does not claim that hook execution or error handling changed in this release. That distinction matters when reviewing a pipeline failure: the useful addition here is an explanation of the outputs, without a stated runtime fix. Teams maintaining their own troubleshooting notes have a concrete upstream reference to check.
Terragrunt recommendations move to latest
Two entries address the recommended Terragrunt version. One bumps the recommendation to v1.0; another says to always recommend the latest Terragrunt.
Read together, they describe a change in how the documentation presents version guidance. The recommendation now points readers toward the latest release. Neither entry supplies migration steps or declares a new minimum supported version. For teams comparing an existing version pin with the docs, the relevant change is the recommendation itself.
The API reference adds gcp_oidc
The Configurations as Code API reference gains a gcp_oidc block. Readers working on that part of their configuration now have an explicit reference entry to consult.
The release notes identify the block by name without listing its fields. This makes the API reference addition useful to track, while leaving the configuration details to the linked change.