chore(rds): postgres 16.13

[phadadi]

Issue # (if applicable)

None

Reason for this change

https://docs.aws.amazon.com/AmazonRDS/latest/PostgreSQLReleaseNotes/postgresql-versions.html#postgresql-versions-version1613

Description of changes

Describe any new or updated permissions being added

Description of how you validated changes

aws rds describe-db-engine-versions --engine aurora-postgresql --output table --query 'DBEngineVersions[*].{Engine:Engine,EngineVersion:EngineVersion}'

------------------------------------------
|        DescribeDBEngineVersions        |
+--------------------+-------------------+
|       Engine       |   EngineVersion   |
+--------------------+-------------------+
...
|  aurora-postgresql |  16.11            |
|  aurora-postgresql |  16.11-limitless  |
|  aurora-postgresql |  16.13            |
...

Checklist

• My code adheres to the CONTRIBUTING GUIDE and DESIGN GUIDELINES

---

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license

[phadadi]

@ozelalisen, could you please review this PR? Thanks!

[mergify]

Thank you for contributing! Your pull request will be updated from main and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork).

[mergify]

Merge Queue Status

• ✅ Entered queue — 2026-04-09 14:59 UTC · Rule: default-squash
• 🚫 Left the queue — 2026-04-09 16:14 UTC · at 2bb216e39c143795c253417c3400e813cb24a6d6

This pull request spent 1 hour 15 minutes 24 seconds in the queue, with no time running CI.

Reason

The pull request can't be updated

For security reasons, Mergify can't update this pull request. Try updating locally.
GitHub response: refusing to allow a GitHub App to create or update workflow .github/workflows/spec-update.yml without workflows permission

Hint

You should update or rebase your pull request manually. If you do, this pull request will automatically be requeued once the queue conditions match again.
If you think this was a flaky issue, you can requeue the pull request, without updating it, by posting a @mergifyio queue comment.

[mergify]

Thank you for contributing! Your pull request will be updated from main and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork).

[mergify]

Thank you for contributing! Your pull request will be updated from main and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork).

[mergify]

Merge Queue Status

• ✅ Entered queue — 2026-04-09 18:14 UTC · Rule: default-squash
• ✅ Checks skipped · PR is already up-to-date
• ✅ Merged — 2026-04-09 18:14 UTC · at 3703f438d4041d5da14ee35d3c9b4f690d81aeb9

This pull request spent 10 seconds in the queue, including 1 second running CI.

Required conditions to merge

• #approved-reviews-by >= 1 [🛡 GitHub branch protection]
  • chore(rds): postgres 16.13 #37540
• #changes-requested-reviews-by = 0 [🛡 GitHub branch protection]
  • chore(rds): postgres 16.13 #37540
• any of [🛡 GitHub branch protection]:
  • check-success = validate-pr
  • check-neutral = validate-pr
  • check-skipped = validate-pr
• any of [🛡 GitHub branch protection]:
  • check-success = build
  • check-neutral = build
  • check-skipped = build

[github-actions]

Comments on closed issues and PRs are hard for our team to see.
If you need help, please open a new issue that references this one.