Update Gruntwork Releases as of 2026-03-31#3054
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Contributor
|
Note Reviews pausedIt looks like this branch is under active development. To avoid overwhelming you with review comments due to an influx of new commits, CodeRabbit has automatically paused this review. You can configure this behavior by changing the Use the following commands to manage reviews:
Use the checkboxes below for quick actions:
WalkthroughThis PR adds a new Gruntwork release page for 2026-03, updates the stay-up-to-date guide and releases index cards to surface 2026-03 (removing/replacing the prior card), expands the 2026-02 release notes with terraform-aws-data-storage v0.47.0 details, and refreshes several DOCS-SOURCER metadata hashes. All changes are documentation-only. Changes
Sequence Diagram(s)(Skipped — documentation edits only.) Estimated code review effort🎯 3 (Moderate) | ⏱️ ~20 minutes Possibly related PRs
Suggested reviewers
Poem
🚥 Pre-merge checks | ✅ 3✅ Passed checks (3 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
Contributor
There was a problem hiding this comment.
🧹 Nitpick comments (2)
docs/guides/stay-up-to-date/releases/2026-03/index.md (2)
39-39: Consider more concise wording.The phrase "Due to the fact that" can be simplified to "Since" or "Because" for improved readability.
✏️ Suggested improvement
-Note that although this isn't a breaking change, this does require an update to the [manifest](https://boilerplate.gruntwork.io/advanced/manifest/) schema, and as such you'll want to ensure that your manifest parsing isn't impacted. Due to the fact that a field has only been added, this risk is minimal if you use a modern YAML/JSON parser. +Note that although this isn't a breaking change, this does require an update to the [manifest](https://boilerplate.gruntwork.io/advanced/manifest/) schema, and as such you'll want to ensure that your manifest parsing isn't impacted. Since only a field has been added, this risk is minimal if you use a modern YAML/JSON parser.🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@docs/guides/stay-up-to-date/releases/2026-03/index.md` at line 39, The sentence uses the wordy phrase "Due to the fact that"; replace it with a concise alternative such as "Since" or "Because" in the paragraph that begins "Note that although this isn't a breaking change..." in docs/guides/stay-up-to-date/releases/2026-03/index.md so the line reads e.g. "Since a field has only been added, this risk is minimal if you use a modern YAML/JSON parser." to improve readability while preserving meaning.
156-156: Inconsistent list indentation detected.Several list items have inconsistent indentation (0 spaces instead of the expected 2 spaces). While this doesn't break rendering, fixing it would improve markdown formatting consistency.
Affected lines: 156, 174-177, 199, 284-285.
Also applies to: 174-177, 199-199, 284-285
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@docs/guides/stay-up-to-date/releases/2026-03/index.md` at line 156, Several unordered list entries in the releases markdown (for example the line starting "* DEV-1385 Fix comment CTA should use per platform terminology by `@Resonance1584` ...") use 0-space indentation instead of the repository's expected 2-space indentation; update those list items (the bullets at the noted positions) to use two leading spaces before the asterisk so the list indentation is consistent across the file (fix the other affected bullets similarly).
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Nitpick comments:
In `@docs/guides/stay-up-to-date/releases/2026-03/index.md`:
- Line 39: The sentence uses the wordy phrase "Due to the fact that"; replace it
with a concise alternative such as "Since" or "Because" in the paragraph that
begins "Note that although this isn't a breaking change..." in
docs/guides/stay-up-to-date/releases/2026-03/index.md so the line reads e.g.
"Since a field has only been added, this risk is minimal if you use a modern
YAML/JSON parser." to improve readability while preserving meaning.
- Line 156: Several unordered list entries in the releases markdown (for example
the line starting "* DEV-1385 Fix comment CTA should use per platform
terminology by `@Resonance1584` ...") use 0-space indentation instead of the
repository's expected 2-space indentation; update those list items (the bullets
at the noted positions) to use two leading spaces before the asterisk so the
list indentation is consistent across the file (fix the other affected bullets
similarly).
ℹ️ Review info
⚙️ Run configuration
Configuration used: Repository UI
Review profile: CHILL
Plan: Pro
Run ID: 9201fea6-7ec1-46d2-aa7c-2ad6b5f8e939
📒 Files selected for processing (4)
docs/guides/stay-up-to-date/index.mddocs/guides/stay-up-to-date/releases/2026-02/index.mddocs/guides/stay-up-to-date/releases/2026-03/index.mddocs/guides/stay-up-to-date/releases/index.md
Contributor
There was a problem hiding this comment.
Actionable comments posted: 3
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In `@docs/guides/stay-up-to-date/releases/2026-02/index.md`:
- Line 836: Fix two typos in the release notes: replace the text "dd ability to
add selection tags optionally to backup-plan" with "Add ability to add selection
tags optionally to backup-plan" (or better: "Add ability to optionally add
selection tags to backup-plan") and correct the module name
"terraterraform-aws-static-assets" to "terraform-aws-static-assets" so exact
module searches resolve correctly.
- Line 254: The markdown lists in the release notes have inconsistent sibling
indentation causing MD005 warnings; locate each affected list block (for example
the bullet line starting "* Upgrade actions/checkout to v6. Pin action versions
by `@Resonance1584`..." and the other blocks around the reported ranges) and make
sibling bullets use a consistent indentation level (choose and apply either no
leading spaces for top-level bullets or a consistent number of spaces, e.g., two
spaces per nesting level), ensure nested sublists are indented one consistent
level deeper than their parent, then re-run markdownlint to confirm MD005 is
resolved.
- Line 772: The "Published" metadata line currently shows malformed list markers
("opensearch, - redshift, - aurora, - rds"); edit the single-line HTML/Markdown
snippet containing the Published text so the "Modules affected" value is a
normal comma-separated list (e.g., "opensearch, redshift, aurora, rds") or
convert it into proper bullet markup; locate the line containing the exact
string "Published: 2/28/2026 | Modules affected:" and remove the stray hyphens
before module names to normalize formatting.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Repository UI
Review profile: CHILL
Plan: Pro
Run ID: e65907c7-ecda-4b7d-bd7f-73a3dd69f428
📒 Files selected for processing (1)
docs/guides/stay-up-to-date/releases/2026-02/index.md
|
|
||
|
|
||
| - dd ability to add selection tags optionally to backup-plan |
Contributor
There was a problem hiding this comment.
Correct user-facing typos in release notes.
- Line 836:
dd ability→Add ability - Line 1042:
terraterraform-aws-static-assetslooks like a typo and should likely beterraform-aws-static-assets
These are minor, but they can confuse readers searching for exact module names.
Suggested fix
-- dd ability to add selection tags optionally to backup-plan
+- Add ability to add selection tags optionally to backup-plan-- Bump `terraterraform-aws-static-assets` to `v1.2.0` for improved compatibility with AWS Provider v6.x
+- Bump `terraform-aws-static-assets` to `v1.2.0` for improved compatibility with AWS Provider v6.xAlso applies to: 1042-1042
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@docs/guides/stay-up-to-date/releases/2026-02/index.md` at line 836, Fix two
typos in the release notes: replace the text "dd ability to add selection tags
optionally to backup-plan" with "Add ability to add selection tags optionally to
backup-plan" (or better: "Add ability to optionally add selection tags to
backup-plan") and correct the module name "terraterraform-aws-static-assets" to
"terraform-aws-static-assets" so exact module searches resolve correctly.
james00012
force-pushed
the
automation/update-releases-as-of-2026-03-31
branch
from
59e916c to
8b7d97a
Compare
Contributor
There was a problem hiding this comment.
♻️ Duplicate comments (3)
docs/guides/stay-up-to-date/releases/2026-02/index.md (3)
836-836:⚠️ Potential issue | 🟡 MinorFix typo: "dd ability" → "Add ability".
This typo was previously flagged but remains unfixed. The line should read "Add ability to add selection tags optionally to backup-plan" (or better: "Add ability to optionally add selection tags to backup-plan").
✏️ Suggested fix
-- dd ability to add selection tags optionally to backup-plan +- Add ability to optionally add selection tags to backup-plan🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@docs/guides/stay-up-to-date/releases/2026-02/index.md` at line 836, Replace the typo "dd ability to add selection tags optionally to backup-plan" with corrected phrasing; locate the exact string "dd ability to add selection tags optionally to backup-plan" and change it to either "Add ability to add selection tags optionally to backup-plan" or preferably "Add ability to optionally add selection tags to backup-plan" so the sentence reads correctly.
254-254:⚠️ Potential issue | 🟡 MinorResolve MD005 list indentation warnings for consistency.
Several list items have inconsistent indentation (0 spaces instead of expected 2), which was previously flagged. Please apply consistent indentation across each list block to resolve the markdownlint MD005 warnings.
Also applies to: 275-275, 293-296, 382-385, 407-407, 445-445, 447-447, 565-565, 587-588
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@docs/guides/stay-up-to-date/releases/2026-02/index.md` at line 254, Multiple markdown list items in index.md violate MD005 due to inconsistent indentation (0 spaces vs expected 2); locate the list blocks containing the bullet text like "Upgrade actions/checkout to v6. Pin action versions by `@Resonance1584`..." and the other affected blocks (around the noted lines) and normalize indentation so nested/list items use two spaces before the dash or asterisk consistently across each list; update the lines referenced (including the other blocks noted: ~275, ~293-296, ~382-385, ~407, ~445, ~447, ~565, ~587-588) to use the same two-space indentation to resolve the MD005 warnings.
1042-1042:⚠️ Potential issue | 🟡 MinorFix typo: "terraterraform" → "terraform".
This typo was previously flagged but remains unfixed. The module name should be
terraform-aws-static-assets, notterraterraform-aws-static-assets.✏️ Suggested fix
-- Bump `terraterraform-aws-static-assets` to `v1.2.0` for improved compatibility with AWS Provider v6.x +- Bump `terraform-aws-static-assets` to `v1.2.0` for improved compatibility with AWS Provider v6.x🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@docs/guides/stay-up-to-date/releases/2026-02/index.md` at line 1042, Replace the misspelled module name 'terraterraform-aws-static-assets' with the correct 'terraform-aws-static-assets' in the release note entry (update the exact string shown in the diff), ensuring the phrasing remains "Bump `terraform-aws-static-assets` to `v1.2.0` for improved compatibility with AWS Provider v6.x".
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Duplicate comments:
In `@docs/guides/stay-up-to-date/releases/2026-02/index.md`:
- Line 836: Replace the typo "dd ability to add selection tags optionally to
backup-plan" with corrected phrasing; locate the exact string "dd ability to add
selection tags optionally to backup-plan" and change it to either "Add ability
to add selection tags optionally to backup-plan" or preferably "Add ability to
optionally add selection tags to backup-plan" so the sentence reads correctly.
- Line 254: Multiple markdown list items in index.md violate MD005 due to
inconsistent indentation (0 spaces vs expected 2); locate the list blocks
containing the bullet text like "Upgrade actions/checkout to v6. Pin action
versions by `@Resonance1584`..." and the other affected blocks (around the noted
lines) and normalize indentation so nested/list items use two spaces before the
dash or asterisk consistently across each list; update the lines referenced
(including the other blocks noted: ~275, ~293-296, ~382-385, ~407, ~445, ~447,
~565, ~587-588) to use the same two-space indentation to resolve the MD005
warnings.
- Line 1042: Replace the misspelled module name
'terraterraform-aws-static-assets' with the correct
'terraform-aws-static-assets' in the release note entry (update the exact string
shown in the diff), ensuring the phrasing remains "Bump
`terraform-aws-static-assets` to `v1.2.0` for improved compatibility with AWS
Provider v6.x".
ℹ️ Review info
⚙️ Run configuration
Configuration used: Repository UI
Review profile: CHILL
Plan: Pro
Run ID: f9cc1001-127f-4157-b965-091ddb92562c
📒 Files selected for processing (1)
docs/guides/stay-up-to-date/releases/2026-02/index.md
james00012
force-pushed
the
automation/update-releases-as-of-2026-03-31
branch
from
f9efbb3 to
fa10617
Compare
Contributor
There was a problem hiding this comment.
Actionable comments posted: 2
♻️ Duplicate comments (3)
docs/guides/stay-up-to-date/releases/2026-02/index.md (3)
772-772:⚠️ Potential issue | 🟡 MinorRemove stray list markers in “Modules affected” metadata.
Line 772 still renders awkwardly as
opensearch, - redshift, - aurora, - rds. Convert this to a normal comma-separated list.Suggested fix
- <small>Published: 2/28/2026 | Modules affected: opensearch, - redshift, - aurora, - rds | <a href="https://github.com/gruntwork-io/terraform-aws-data-storage/releases/tag/v0.47.0">Release notes</a></small> + <small>Published: 2/28/2026 | Modules affected: opensearch, redshift, aurora, rds | <a href="https://github.com/gruntwork-io/terraform-aws-data-storage/releases/tag/v0.47.0">Release notes</a></small>🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@docs/guides/stay-up-to-date/releases/2026-02/index.md` at line 772, The "Published" metadata line currently contains stray list markers ("opensearch, - redshift, - aurora, - rds"); edit the metadata string (the line that begins with <small>Published: ...) to remove the hyphens so the "Modules affected" value is a normal comma-separated list (e.g., "opensearch, redshift, aurora, rds"), preserving the rest of the text and the Release notes link.
836-836:⚠️ Potential issue | 🟡 MinorCorrect typos in release-note bullets.
Line 836 has “dd ability” and Line 1042 has
terraterraform-aws-static-assets; both should be corrected for reader clarity and searchability.Suggested fix
-- dd ability to add selection tags optionally to backup-plan +- Add ability to add selection tags optionally to backup-plan-- Bump `terraterraform-aws-static-assets` to `v1.2.0` for improved compatibility with AWS Provider v6.x +- Bump `terraform-aws-static-assets` to `v1.2.0` for improved compatibility with AWS Provider v6.xAlso applies to: 1042-1042
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@docs/guides/stay-up-to-date/releases/2026-02/index.md` at line 836, Fix two typos in the release-note bullets: replace the text "dd ability to add selection tags optionally to backup-plan" with "Add ability to add selection tags optionally to backup-plan" (capitalize correctly and remove the extra 'd') and change "terraterraform-aws-static-assets" to "terraform-aws-static-assets" so the package name is correct; update the two exact strings found in the document (the first occurrence matching "dd ability to add selection tags optionally to backup-plan" and the occurrence matching "terraterraform-aws-static-assets") to these corrected versions.
254-254:⚠️ Potential issue | 🟡 MinorNormalize list indentation to resolve MD005 warnings.
Several sibling bullets are inconsistently indented (e.g., unindented items mixed with two-space-indented items). Please make each list block use consistent indentation.
Also applies to: 275-275, 293-296, 382-385, 407-407, 445-445, 447-447, 587-588
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@docs/guides/stay-up-to-date/releases/2026-02/index.md` at line 254, Several sibling bullet items in the release notes use mixed indentation (some unindented, some with two spaces) causing MD005 warnings; normalize each list block so all sibling bullets use the same indentation style (choose either no-leading-space or two-space indent) for the bullets such as "Upgrade actions/checkout to v6. Pin action versions by `@Resonance1584`…" and the nearby list blocks referenced in the review (other bullets in the same release notes), ensuring consistent indentation across each block so the markdown linter no longer reports MD005.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In `@docs/guides/stay-up-to-date/releases/2026-02/index.md`:
- Around line 6-7: Replace the incorrect intro phrase "This page is lists all
the updates..." with the corrected text "This page lists all the updates..." by
editing the markdown line that currently contains "This page is lists…"; ensure
the rest of the sentence ("to the [Gruntwork Infrastructure as Code Library]...
that were released in 2026-02. For instructions") remains unchanged.
- Line 428: Update the prose to hyphenate the compound modifiers: change "user
facing" to "user-facing" in the sentence starting with "This release contains
some internal reworks..." (the phrase "user facing impact") and change "self
hosted" to "self-hosted" where it appears later (around the mention of
telemetry/deploys). Ensure both occurrences are replaced with hyphenated forms
so the document reads "user-facing" and "self-hosted."
---
Duplicate comments:
In `@docs/guides/stay-up-to-date/releases/2026-02/index.md`:
- Line 772: The "Published" metadata line currently contains stray list markers
("opensearch, - redshift, - aurora, - rds"); edit the metadata string (the line
that begins with <small>Published: ...) to remove the hyphens so the "Modules
affected" value is a normal comma-separated list (e.g., "opensearch, redshift,
aurora, rds"), preserving the rest of the text and the Release notes link.
- Line 836: Fix two typos in the release-note bullets: replace the text "dd
ability to add selection tags optionally to backup-plan" with "Add ability to
add selection tags optionally to backup-plan" (capitalize correctly and remove
the extra 'd') and change "terraterraform-aws-static-assets" to
"terraform-aws-static-assets" so the package name is correct; update the two
exact strings found in the document (the first occurrence matching "dd ability
to add selection tags optionally to backup-plan" and the occurrence matching
"terraterraform-aws-static-assets") to these corrected versions.
- Line 254: Several sibling bullet items in the release notes use mixed
indentation (some unindented, some with two spaces) causing MD005 warnings;
normalize each list block so all sibling bullets use the same indentation style
(choose either no-leading-space or two-space indent) for the bullets such as
"Upgrade actions/checkout to v6. Pin action versions by `@Resonance1584`…" and the
nearby list blocks referenced in the review (other bullets in the same release
notes), ensuring consistent indentation across each block so the markdown linter
no longer reports MD005.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Repository UI
Review profile: CHILL
Plan: Pro
Run ID: 8ee454f9-5347-464c-876f-962d0600f0ad
📒 Files selected for processing (1)
docs/guides/stay-up-to-date/releases/2026-02/index.md
Comment on lines
+6
to
+7
| This page is lists all the updates to the [Gruntwork Infrastructure as Code | ||
| Library](https://gruntwork.io/infrastructure-as-code-library/) that were released in 2026-02. For instructions |
Contributor
There was a problem hiding this comment.
Fix sentence grammar in the page intro.
Line 6 currently says “This page is lists…”. Please change to “This page lists…”.
Suggested fix
-This page is lists all the updates to the [Gruntwork Infrastructure as Code
+This page lists all the updates to the [Gruntwork Infrastructure as Code🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@docs/guides/stay-up-to-date/releases/2026-02/index.md` around lines 6 - 7,
Replace the incorrect intro phrase "This page is lists all the updates..." with
the corrected text "This page lists all the updates..." by editing the markdown
line that currently contains "This page is lists…"; ensure the rest of the
sentence ("to the [Gruntwork Infrastructure as Code Library]... that were
released in 2026-02. For instructions") remains unchanged.
| <div style={{"overflow":"hidden","textOverflow":"ellipsis","display":"-webkit-box","WebkitLineClamp":10,"lineClamp":10,"WebkitBoxOrient":"vertical"}}> | ||
|
|
||
| :nut_and_bolt: This release contains some internal reworks around how we collect and process Terragrunt output during plan/apply, as well as adding the Terragrunt [Run Report](https://terragrunt.gruntwork.io/docs/features/run-report/) to Job artifacts for future use. There is additional internal Gruntwork telemetry around deploys being added, but we expect no user facing impact from this release. |
Contributor
There was a problem hiding this comment.
Hyphenate compound modifiers for cleaner user-facing text.
Please use hyphenation in “user-facing” (Line 428) and “self-hosted” (Line 444).
Also applies to: 444-444
🧰 Tools
🪛 LanguageTool
[grammar] ~428-~428: Use a hyphen to join words.
Context: ...ploys being added, but we expect no user facing impact from this release.
**...
(QB_NEW_EN_HYPHEN)
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@docs/guides/stay-up-to-date/releases/2026-02/index.md` at line 428, Update
the prose to hyphenate the compound modifiers: change "user facing" to
"user-facing" in the sentence starting with "This release contains some internal
reworks..." (the phrase "user facing impact") and change "self hosted" to
"self-hosted" where it appears later (around the mention of telemetry/deploys).
Ensure both occurrences are replaced with hyphenated forms so the document reads
"user-facing" and "self-hosted."
The v0.47.0 terraform-aws-data-storage release notes originally had relative links (/modules/backup-plan, etc.) that broke the docs build. The GitHub release was since corrected to use absolute URLs — re-running docs-sourcer picks up the fix.
oredavids
force-pushed
the
automation/update-releases-as-of-2026-03-31
branch
from
e89b71c to
76198d7
Compare
Contributor
|
@james00012 the final fix required rerunning the releases plugin to pull the updated content from the release notes. |
yhakbar
approved these changes
Apr 14, 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
4 participants
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.
Update Gruntwork releases as of 2026-03-31
Summary by CodeRabbit