chore: bump version to correct new version for potential release

[samrose]

Previous releases had set the wrong/conflicting version which made the ami release workflow fail. This PR advances the release to the correct new numbers to create a release without failure.

Summary by CodeRabbit

• Chores
  • Updated PostgreSQL package versions across multiple releases to the latest patch updates (including updates for recent 17.x and 15.x releases).

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[coderabbitai]

Walkthrough

Updated version strings in the postgres_release mapping within ansible/vars.yml. Three PostgreSQL variants were bumped: postgresorioledb-17, postgres17, and postgres15 to new patch versions.

Changes

Cohort / File(s)	Summary
PostgreSQL Release Version Updates ansible/vars.yml	Updated postgres_release entries: postgresorioledb-17 "17.6.0.025-orioledb" → "17.6.0.027-orioledb"; postgres17 "17.6.1.068" → "17.6.1.070"; postgres15 "15.14.1.068" → "15.14.1.070".

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Poem

🐰 New versions hop into view,
Bumps and patches, tidy and true,
Numbers climb, quiet and spry,
I nibble bugs as they pass by,
Hooray for updates—hop, hop, high! 🚀

🚥 Pre-merge checks | ✅ 2 | ❌ 1

❌ Failed checks (1 inconclusive)

Check name	Status	Explanation	Resolution
Description check	❓ Inconclusive	The description provides context about the version conflict issue and the purpose of the changes, but lacks the structure specified in the repository's template which requires selecting a specific sub-template format.	Use one of the repository's provided description templates (Default or Extension Upgrade) to ensure consistency with the repository's documentation standards.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title accurately describes the main change: bumping PostgreSQL version numbers in the ansible/vars.yml configuration file for a release.
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.}

---

📜 Recent review details

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 118fa39 and 0b08219.

📒 Files selected for processing (1)

• ansible/vars.yml

🚧 Files skipped from review as they are similar to previous changes (1)

• ansible/vars.yml

---

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.}