Update releases.properties from release 2025.11.22

[N6REJ]

User description

🤖 Automated Releases Properties Update

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

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/2025.11.22

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

---

PR Type

Enhancement

---

Description

• Removed duplicate PostgreSQL version entries from releases.properties

• Added new version entry 2025.7.2.7 with PostgreSQL 18.1

• Cleaned up redundant entries from 2025.11.22 release

• Maintained semver ordering with newest versions first

---

Diagram Walkthrough

flowchart LR
  A["releases.properties<br/>2025.11.22 release"] -->|Remove duplicates| B["Cleaned entries<br/>18.1, 16.11, 15.15, 14.20, 13.23"]
  B -->|Add new version| C["2025.7.2.7 entry<br/>PostgreSQL 18.1"]
  C -->|Maintain ordering| D["Updated file<br/>Semver sorted"]

Loading

File Walkthrough

Relevant files

Configuration changes

releases.properties Remove duplicates and add PostgreSQL 18.1 version                releases.properties Removed 5 duplicate version entries (18.1, 16.11, 15.15, 14.20, 13.23) that were pointing to 2025.11.22 release Added new version entry 2025.7.2.7 with PostgreSQL 18.1 download URL Reduced file from 26 lines to 22 lines by eliminating redundant entries Maintained semver ordering with newest versions listed first +1/-6

---

[github-actions]

🐘 PostgreSQL Module Tests - Results

Test Date: 2025-12-22 03:18:46 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]

PR Compliance Guide 🔍

Below is a summary of compliance checks for this PR:

Security Compliance
⚪	Supply chain risk Description: The new 2025.7.2.7 entry points to a remotely hosted .7z artifact URL without any accompanying integrity mechanism (e.g., checksum/signature pinning), which can enable a supply-chain compromise if the referenced GitHub release asset is replaced or the release account is compromised. releases.properties [1-1] Referred Code 2025.7.2.7 = https://github.com/Bearsampp/module-postgresql/releases/download/2025.11.22/bearsampp-postgresql-18.1-2025.7.2.7z 17.5 = https://github.com/Bearsampp/module-postgresql/releases/download/2025.7.2/bearsampp-postgresql-17.5-2025.7.2.7z
Ticket Compliance
⚪	🎫 No ticket provided Create ticket/issue
Codebase Duplication Compliance
⚪	Codebase context is not defined Follow the guide to enable codebase context checks.
Custom Compliance
🟢	Generic: Comprehensive Audit Trails Objective: To create a detailed and reliable record of critical system actions for security analysis and compliance. Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Meaningful Naming and Self-Documenting Code Objective: Ensure all identifiers clearly express their purpose and intent, making code self-documenting Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Robust Error Handling and Edge Case Management Objective: Ensure comprehensive error handling that provides meaningful context and graceful degradation Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Secure Error Handling Objective: To prevent the leakage of sensitive system information through error messages while providing sufficient detail for internal debugging. Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Secure Logging Practices Objective: To ensure logs are useful for debugging and auditing without exposing sensitive information like PII, PHI, or cardholder data. Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Security-First Input Validation and Data Handling Objective: Ensure all data inputs are validated, sanitized, and handled securely to prevent vulnerabilities Status: Passed Learn more about managing compliance generic rules or creating your own custom rules

Compliance status legend

🟢 - Fully Compliant
🟡 - Partial Compliant
🔴 - Not Compliant
⚪ - Requires Further Human Verification
🏷️ - Compliance label

[qodo-code-review]

PR Code Suggestions ✨

Explore these optional code suggestions:

Category	Suggestion	Impact
Possible issue	Correct the version key inconsistency Change the property key from 2025.7.2.7 to 18.1 to match the PostgreSQL version in the download URL and maintain consistency with other entries. releases.properties [1] -+2025.7.2.7 = https://github.com/Bearsampp/module-postgresql/releases/download/2025.11.22/bearsampp-postgresql-18.1-2025.7.2.7z +18.1 = https://github.com/Bearsampp/module-postgresql/releases/download/2025.11.22/bearsampp-postgresql-18.1-2025.7.2.7z Apply / Chat Suggestion importance[1-10]: 10 __ Why: This suggestion correctly identifies a critical error where the property key 2025.7.2.7 does not match the PostgreSQL version 18.1 in the URL, which would break the version mapping.	High
More