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 versions across multiple releases to latest patch versions.

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

[coderabbitai]

Walkthrough

Updated version strings in the postgres_release mapping within the Ansible configuration. Three PostgreSQL variants were bumped to newer patch versions: postgresorioledb-17 to 17.6.0.026-orioledb, postgres17 to 17.6.1.069, and postgres15 to 15.14.1.069.

Changes

Cohort / File(s)	Summary
PostgreSQL Release Version Updates ansible/vars.yml	Updated three entries in the postgres_release mapping: postgresorioledb-17 (17.6.0.024 → 17.6.0.026), postgres17 (17.6.1.067 → 17.6.1.069), and postgres15 (15.14.1.067 → 15.14.1.069)

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Possibly related PRs

• fix: set restart limits to 0 to prevent being marked as failed #1952 — Updates the same postgres_release mapping in ansible/vars.yml with PostgreSQL version string changes

Suggested reviewers

• pcnc
• darora
• delgado3d

Poem

🐰 Hop, hop, versions rise and fall,
Patch by patch, we heed the call,
Six to twenty-six, one to nine,
Each release, a bit more fine! ✨

Pre-merge checks

❌ Failed checks (1 inconclusive)

Check name	Status	Explanation	Resolution
Description check	❓ Inconclusive	The description lacks structure and doesn't follow the repository's template which specifies selecting a sub-template (Default or Extension Upgrade).	Use the appropriate description template from the repository; select either Default or Extension Upgrade template to provide structured context for reviewers.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title accurately summarizes the main change: version bumps in postgres_release mapping to correct versions for a potential release.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

---

📜 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 963c42d and 118fa39.

📒 Files selected for processing (1)

• ansible/vars.yml

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (5)

• GitHub Check: run-tests / build (17)
• GitHub Check: run-tests / build (15)
• GitHub Check: run-testinfra / test-ami-nix (orioledb-17)
• GitHub Check: run-testinfra / test-ami-nix (17)
• GitHub Check: run-testinfra / test-ami-nix (15)

🔇 Additional comments (1)

ansible/vars.yml (1)

13-15: Version bumps are consistent and well-structured.

All three PostgreSQL version strings are incremented uniformly (+2 in the final component), and the old version references have been completely removed from the codebase with no stale references remaining. The changes are isolated to ansible/vars.yml and properly formatted.

Verify that these versions are available in your package repositories and that the deployment workflow completes successfully with the new version strings.

---

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