Update releases.properties from release 2026.6.2

[N6REJ]

🤖 Automated Releases Properties Update

This PR updates the releases.properties file with new versions from release 2026.6.2.

Changes:

• Extracted .7z assets from the release
• Added version entries with download URLs
• Maintained semver ordering (newest first)

Release URL: https://github.com/Bearsampp/module-postgresql/releases/tag/2026.6.2

Next Steps:

1. ⏳ Link validation will run automatically
2. ✅ Once validation passes, this PR will auto-merge
3. ❌ If validation fails, please review and fix invalid URLs

[qodo-code-review]

Review Summary by Qodo

Add PostgreSQL versions from release 2026.6.2

✨ Enhancement

Walkthroughs

Description

• Added 5 new PostgreSQL versions from release 2026.6.2
• Updated existing version entries with newer release URLs
• Maintained semver ordering with newest versions first
• New versions: 18.4, 17.10, 16.14, 15.18, 14.23

Diagram

flowchart LR
  A["Release 2026.6.2"] -->|"Extract .7z assets"| B["New Versions"]
  B -->|"18.4, 17.10, 16.14, 15.18, 14.23"| C["Update releases.properties"]
  C -->|"Maintain semver order"| D["Updated Configuration"]

Loading

File Changes

1. releases.properties ⚙️ Configuration changes +7/-2

Add new PostgreSQL versions and update URLs

• Added 5 new PostgreSQL version entries from release 2026.6.2 (18.4, 17.10, 16.14, 15.18, 14.23)
• Updated download URLs for existing versions (18.1, 14.22) to point to newer release 2026.6.2
• Maintained semantic versioning order with newest versions listed first
• All entries reference .7z asset downloads from GitHub releases

releases.properties

---

[qodo-code-review]

Code Review by Qodo

🐞 Bugs (1) 📘 Rule violations (0) 🔗 Cross-repo conflicts (0)

1. CI skips release update 🐞 Bug ☼ Reliability

Description

For pull_request events, the postgresql-test workflow only derives versions from changed /bin paths
or from numeric patterns in the PR title; a PR that only edits releases.properties will typically
produce an empty version list and skip the Windows download/extract smoke tests for the newly added
versions.

Code

releases.properties[R1-4]

Evidence

This PR only changes releases.properties (adding new versions at the top). In PR mode, the
workflow’s primary detection only extracts versions from changed /bin/postgresql... paths; if none
are found, it falls back to extracting X.Y patterns from the PR title and will set VERSIONS="[]"
when none of those values are valid keys in releases.properties, which prevents the test job from
running.

releases.properties[1-4]
.github/workflows/postgresql-test.yml[75-165]

Agent prompt

The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

### Issue description
`postgresql-test.yml` skips testing when a PR only updates `releases.properties`, because version detection does not look at that file’s changes and the PR-title regex commonly extracts unrelated numbers (e.g., release tag fragments), resulting in `VERSIONS="[]"` and the test job being skipped.

### Issue Context
This PR adds new top versions in `releases.properties`, but the PR-based version detection in the CI workflow only checks changed `/bin` paths and then falls back to extracting `X.Y` patterns from the PR title.

### Fix Focus Areas
- .github/workflows/postgresql-test.yml[75-165]

### Implementation notes
- Add a detection path for PRs that parses added/modified keys in `releases.properties` (e.g., via `git diff` against the base SHA and extracting `^[0-9]+\.[0-9]+` keys from added lines).
- Use those detected keys to populate `VERSIONS` (and optionally cap to the newest N).
- Keep the existing `/bin` and title-based fallbacks as secondary paths.

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

---

[github-actions]

🐘 PostgreSQL Module Tests - Results

Test Date: 2026-06-03 04:23:43 UTC
Status: ⏭️ Tests skipped - no versions to test

ℹ️ Why were tests skipped?

Tests are only run when:

• releases.properties is modified with new/updated versions, OR
• PR title contains version numbers (e.g., "17.2", "16.6") that exist in releases.properties

To trigger tests:

1. Add version numbers to your PR title (e.g., "Update docs for PostgreSQL 17.2")
2. Or modify releases.properties to add/update versions
3. Or manually trigger the workflow from the Actions tab

[qodo-code-review]

1. Ci skips release update 🐞 Bug ☼ Reliability

For pull_request events, the postgresql-test workflow only derives versions from changed /bin paths
or from numeric patterns in the PR title; a PR that only edits releases.properties will typically
produce an empty version list and skip the Windows download/extract smoke tests for the newly added
versions.

Agent Prompt

### Issue description
`postgresql-test.yml` skips testing when a PR only updates `releases.properties`, because version detection does not look at that file’s changes and the PR-title regex commonly extracts unrelated numbers (e.g., release tag fragments), resulting in `VERSIONS="[]"` and the test job being skipped.

### Issue Context
This PR adds new top versions in `releases.properties`, but the PR-based version detection in the CI workflow only checks changed `/bin` paths and then falls back to extracting `X.Y` patterns from the PR title.

### Fix Focus Areas
- .github/workflows/postgresql-test.yml[75-165]

### Implementation notes
- Add a detection path for PRs that parses added/modified keys in `releases.properties` (e.g., via `git diff` against the base SHA and extracting `^[0-9]+\.[0-9]+` keys from added lines).
- Use those detected keys to populate `VERSIONS` (and optionally cap to the newest N).
- Keep the existing `/bin` and title-based fallbacks as secondary paths.

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools