PostgreSQL minor version updates

[maqeel75]

Summary

• Bumped PostgreSQL 16 from 16.12 to 16.13
• Bumped PostgreSQL 17 from 17.8 to 17.9
• Bumped PostgreSQL 18 from 18.2 to 18.3
• Bumped PostGIS from 3.5.4 to 3.5.5 across all PG versions (standard flavor)

Changes

• Renamed all package list files (amd64 & arm64) to reflect the new PG minor versions
• Updated package versions within those files for pgedge-postgresql16/17/18
• Updated postgis35_16/17/18 to 3.5.5 in all standard package lists
• Updated postgres_version values in scripts/build_pgedge_images.py for all three major PG versions

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between d248f1b and 1127652.

📒 Files selected for processing (13)

• packagelists/amd64/pg16.13-spock5.0.5-minimal.txt
• packagelists/amd64/pg16.13-spock5.0.5-standard.txt
• packagelists/amd64/pg17.9-spock5.0.5-minimal.txt
• packagelists/amd64/pg17.9-spock5.0.5-standard.txt
• packagelists/amd64/pg18.3-spock5.0.5-minimal.txt
• packagelists/amd64/pg18.3-spock5.0.5-standard.txt
• packagelists/arm64/pg16.13-spock5.0.5-minimal.txt
• packagelists/arm64/pg16.13-spock5.0.5-standard.txt
• packagelists/arm64/pg17.9-spock5.0.5-minimal.txt
• packagelists/arm64/pg17.9-spock5.0.5-standard.txt
• packagelists/arm64/pg18.3-spock5.0.5-minimal.txt
• packagelists/arm64/pg18.3-spock5.0.5-standard.txt
• scripts/build_pgedge_images.py

---

📝 Walkthrough

Walkthrough

Package versions updated across PostgreSQL 16, 17, and 18 builds for amd64 and arm64 architectures. PostgreSQL versions incremented (16.12→16.13, 17.8→17.9, 18.2→18.3) and PostGIS updated from 3.5.4→3.5.5 in standard builds. Build script version literals updated accordingly.

Changes

Cohort / File(s)	Summary
PostgreSQL 16 Package Lists packagelists/amd64/pg16.13-spock5.0.5-minimal.txt, packagelists/amd64/pg16.13-spock5.0.5-standard.txt, packagelists/arm64/pg16.13-spock5.0.5-minimal.txt, packagelists/arm64/pg16.13-spock5.0.5-standard.txt	Updated pgedge-postgresql16 from 16.12-1.el9 to 16.13-1.el9. Standard builds also updated pgedge-postgis35_16 from 3.5.4-1.el9 to 3.5.5-1.el9.
PostgreSQL 17 Package Lists packagelists/amd64/pg17.9-spock5.0.5-minimal.txt, packagelists/amd64/pg17.9-spock5.0.5-standard.txt, packagelists/arm64/pg17.9-spock5.0.5-minimal.txt, packagelists/arm64/pg17.9-spock5.0.5-standard.txt	Updated pgedge-postgresql17 from 17.8-1.el9 to 17.9-1.el9. Standard builds also updated pgedge-postgis35_17 from 3.5.4-1.el9 to 3.5.5-1.el9.
PostgreSQL 18 Package Lists packagelists/amd64/pg18.3-spock5.0.5-minimal.txt, packagelists/amd64/pg18.3-spock5.0.5-standard.txt, packagelists/arm64/pg18.3-spock5.0.5-minimal.txt, packagelists/arm64/pg18.3-spock5.0.5-standard.txt	Updated pgedge-postgresql18 from 18.2-1.el9 to 18.3-1.el9. Standard builds also updated pgedge-postgis35_18 from 3.5.4-1.el9 to 3.5.5-1.el9.
Build Script scripts/build_pgedge_images.py	Updated PostgreSQL version literals for image generation: 16.12→16.13, 17.8→17.9, 18.2→18.3.

Poem

🐰 Hop, hop, the versions dance and play,
PostgreSQL versions bright and new today!
Sixteen, seventeen, eighteen all agree,
PostGIS joins the spree at three-five-five, you'll see! 🎉

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly and concisely summarizes the main change: updating PostgreSQL to minor versions across the changeset.
Description check	✅ Passed	The description is directly related to the changeset, providing specific details about PostgreSQL and PostGIS version bumps and file changes.
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 docstrings (stacked PR)
• 📝 Generate docstrings (commit on current branch)

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch feature/BR-503/OOC-updates

Tip

Try Coding Plans. Let us write the prompt for your AI agent so you can ship faster (with fewer bugs).
Share your feedback on Discord.

---

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