Update releases.properties from release 2026.3.8

[N6REJ]

🤖 Automated Releases Properties Update

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

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

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

✨ Enhancement

Walkthroughs

Description

• Add five new PostgreSQL versions from release 2026.3.8
• Versions include 18.3, 17.9, 16.13, 15.17, 14.22
• Maintain semver ordering with newest versions first
• Update download URLs pointing to 2026.3.8 release assets

Diagram

flowchart LR
  A["Release 2026.3.8"] -->|"Extract assets"| B["5 new versions"]
  B -->|"Add entries"| C["releases.properties"]
  C -->|"Maintain order"| D["Semver sorted list"]

Loading

File Changes

1. releases.properties ✨ Enhancement +5/-0

Add five new PostgreSQL versions from 2026.3.8

• Added version 18.3 with download URL from 2026.3.8 release
• Added version 17.9 with download URL from 2026.3.8 release
• Added version 16.13 with download URL from 2026.3.8 release
• Added version 15.17 with download URL from 2026.3.8 release
• Added version 14.22 with download URL from 2026.3.8 release
• Maintained semantic versioning order with newest versions first

releases.properties

---

[qodo-code-review]

Code Review by Qodo

🐞 Bugs (2) 📘 Rule violations (0) 📎 Requirement gaps (0)

1. CI tests may be skipped 🐞 Bug ⛯ Reliability

Description

Because this PR only changes releases.properties and the automated PR title contains only a
release date (e.g., 2026.3.8), the PR test workflow’s version-detection fallback can extract an
invalid “version” (e.g., 2026.3) and then skip PostgreSQL install/start tests entirely. This
increases the chance of merging new release entries that were never actually
downloaded/extracted/started in CI.

Code

releases.properties[R1-3]

+18.3 = https://github.com/Bearsampp/module-postgresql/releases/download/2026.3.8/bearsampp-postgresql-18.3-2025.3.8.7z
18.1 = https://github.com/Bearsampp/module-postgresql/releases/download/2025.11.22/bearsampp-postgresql-18.1-2025.7.2.7z
+17.9 = https://github.com/Bearsampp/module-postgresql/releases/download/2026.3.8/bearsampp-postgresql-17.9-2025.3.8.7z

Evidence

The auto-update workflow creates PR titles in the form “Update releases.properties from release
<tag>”, which for this PR is a date-like string (2026.3.8) rather than module versions like
18.3. In PR runs, postgresql-test.yml first looks for changed /bin/postgresqlX.Y/ paths; if
none are present (true for this PR), it falls back to extracting [0-9]+\.[0-9]+ from the PR title,
validates those extracted values as keys in releases.properties, and skips tests when none
match—so properties-only release PRs are likely to skip functional testing.

.github/workflows/update-releases-properties.yml[252-270]
.github/workflows/postgresql-test.yml[89-143]
releases.properties[1-3]

Agent prompt

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

### Issue description
Properties-only automated release PRs can skip functional PostgreSQL testing because the PR title contains only a release date (e.g., `2026.3.8`), which the PR-title regex interprets as `2026.3` and cannot validate against keys like `18.3`.

### Issue Context
The PR is created by automation and is intended to be auto-merged after link validation; without the functional test job running, archives may be unverified (extractability/startability).

### Fix Focus Areas
- .github/workflows/postgresql-test.yml[89-153]
- .github/workflows/update-releases-properties.yml[252-270]

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

---

2. Suspicious URL year mismatch 🐞 Bug ✓ Correctness

Description

All newly added URLs use the release tag path .../download/2026.3.8/ but the asset filenames end
with -2025.3.8.7z. If this is a copy/paste/year typo, the URLs will 404 and break link validation
and downstream downloads.

Code

releases.properties[1]

+18.3 = https://github.com/Bearsampp/module-postgresql/releases/download/2026.3.8/bearsampp-postgresql-18.3-2025.3.8.7z

Evidence

The added entries consistently embed 2026.3.8 in the GitHub release download path but embed
2025.3.8 in the asset filename, which is an unusual pattern and a common cause of broken URLs. The
repo’s link-validation workflow will fail the PR if any of these URLs are not reachable (HEAD/GET).

releases.properties[1-3]
releases.properties[10-17]
releases.properties[26-29]
.github/workflows/validate-properties-links.yml[85-143]

Agent prompt

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

### Issue description
New `releases.properties` entries appear to mix two different dates (`2026.3.8` in the download path vs `2025.3.8` in the filename). This often indicates a broken URL.

### Issue Context
CI link validation will fail if these URLs 404, and users/CI downloads will break.

### Fix Focus Areas
- releases.properties[1-3]
- releases.properties[10-17]
- releases.properties[26-29]

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

---

ⓘ The new review experience is currently in Beta. Learn more

[github-actions]

🐘 PostgreSQL Module Tests - Results

Test Date: 2026-03-08 06:21:04 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