Skip to content

Update Gruntwork Releases as of 2026-03-31#3054

Open
gruntwork-ci wants to merge 1 commit intomainfrom
automation/update-releases-as-of-2026-03-31
Open

Update Gruntwork Releases as of 2026-03-31#3054
gruntwork-ci wants to merge 1 commit intomainfrom
automation/update-releases-as-of-2026-03-31

Conversation

@gruntwork-ci
Copy link
Copy Markdown
Contributor

@gruntwork-ci gruntwork-ci commented Apr 1, 2026

Update Gruntwork releases as of 2026-03-31

Summary by CodeRabbit

  • Documentation
    • Added 2026-03 release guide documenting updates across multiple Gruntwork libraries
    • Updated 2026-02 release guide with new terraform-aws-data-storage module (v0.47.0), including a new OpenSearch module and deprecation notices for Lambda snapshot modules
    • Updated releases index page to feature the latest 2026-03 release

@vercel
Copy link
Copy Markdown

vercel bot commented Apr 1, 2026

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
docs Error Error Apr 1, 2026 8:33am

Request Review

@coderabbitai
Copy link
Copy Markdown
Contributor

coderabbitai bot commented Apr 1, 2026

Walkthrough

This PR adds documentation for Gruntwork's 2026-03 release cycle by creating a new comprehensive release index page, updating the stay-up-to-date guide card listings, and expanding the 2026-02 release documentation with additional module information and changelog details. All changes are documentation-only with metadata hash updates.

Changes

Cohort / File(s) Summary
Release Index Updates
docs/guides/stay-up-to-date/index.md, docs/guides/stay-up-to-date/releases/index.md
Updated releases card listings to include the new 2026-03 release, replaced outdated 2024-12 card with 2026-03, and refreshed DOCS-SOURCER metadata hashes to reflect the catalog changes.
New 2026-03 Release Documentation
docs/guides/stay-up-to-date/releases/2026-03/index.md
Created comprehensive new release index page documenting all 2026-03 updates across 9 repositories (boilerplate, pipelines-cli, terraform-aws-cache, terraform-aws-eks, and others) with version details, publication dates, release notes links, and condensed changelogs.
2026-02 Release Enhancement
docs/guides/stay-up-to-date/releases/2026-02/index.md
Expanded release documentation with new terraform-aws-data-storage v0.47.0 section, marking opensearch as NEW and multiple Lambda snapshot modules as DEPRECATED, plus additional per-module feature notes for OpenSearch, Redshift, RDS, Aurora, and RDS variants.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~12 minutes

Possibly related PRs

Suggested reviewers

  • oredavids
  • ZachGoldberg

Poem

📚 A new release emerges, 2026-03 takes its place,
Cards shuffle through the catalog, keeping pace,
From data storage to service mesh so fine,
The changelog whispers of modules redesigned,
Staying up-to-date has never looked so bright! ✨

🚥 Pre-merge checks | ✅ 3
✅ Passed checks (3 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title clearly summarizes the main purpose of the pull request: updating Gruntwork release documentation for the 2026-03 period, with a specific date marker.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch automation/update-releases-as-of-2026-03-31

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.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

Copy link
Copy Markdown
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🧹 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

📥 Commits

Reviewing files that changed from the base of the PR and between 1fe5f4d and fa10617.

📒 Files selected for processing (4)
  • docs/guides/stay-up-to-date/index.md
  • docs/guides/stay-up-to-date/releases/2026-02/index.md
  • docs/guides/stay-up-to-date/releases/2026-03/index.md
  • docs/guides/stay-up-to-date/releases/index.md

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant