Update engine version date in aurora-postgres.yaml

[goruha]

what

• Update engine version date in aurora-postgres.yaml

why

• 13.12 is EOL on AWS

references

• https://linear.app/cloudposse/issue/DEV-3640/decommission-aurora-postgresql-cluster-in-sandbox-aws-799847381734-us

Summary by CodeRabbit

• Documentation
  • Updated comments to clarify the Aurora PostgreSQL engine version, refreshing the “latest supported version” date to 10/08/2025 for accuracy.
  • No functional, configuration, or behavioral changes; existing engine_version remains unchanged.
  • Improves clarity for users reviewing stack configurations and planning upgrades.

[goruha]

/terratest

[coderabbitai]

Warning

Rate limit exceeded

@goruha has exceeded the limit for the number of commits or files that can be reviewed per hour. Please wait 3 minutes and 34 seconds before requesting another review.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

📥 Commits

Reviewing files that changed from the base of the PR and between 99e209f and e328596.

📒 Files selected for processing (1)

• test/fixtures/stacks/catalog/aurora-postgres.yaml (1 hunks)

Walkthrough

Updated a documentation comment in a test fixture YAML file to reflect a new date for the engine_version note; no functional or configuration changes.

Changes

Cohort / File(s)	Summary
Docs comment update test/fixtures/stacks/catalog/aurora-postgres.yaml	Updated comment to "Latest supported version as of 10/08/2025"; retained engine_version value "13.22". No behavioral changes.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

A nibble of notes in YAML land,
I twitch my whiskers, pen in hand—
The date now fresh, the configs stay,
Same burrow paths, a brighter day.
Thump-thump! I sign with fluffy cheer,
Docs updated—carrots near! 🥕

Pre-merge checks and finishing touches

✅ 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 accurately summarizes the main change of updating the engine version date in the aurora-postgres.yaml file and matches the documented modification. It is concise, specific, and free of unnecessary details. This makes the pull request's intent clear to reviewers at a glance.
Docstring Coverage	✅ Passed	No functions found in the changes. Docstring coverage check skipped.

---

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

• X
• Mastodon
• Reddit
• LinkedIn

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

[goruha]

/terratest