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

• Added five new PostgreSQL versions from release 2025.11.22

• Updated version entries: 18.1, 17.7, 16.11, 15.15, 14.20, 13.23

• Maintained semver ordering with newest versions first

• All entries point to official GitHub release downloads

---

Diagram Walkthrough

flowchart LR
  A["Release 2025.11.22"] -->|"Extract versions"| B["New PostgreSQL Versions"]
  B -->|"18.1, 17.7, 16.11, 15.15, 14.20, 13.23"| C["Update releases.properties"]
  C -->|"Maintain semver order"| D["Updated Configuration"]

Loading

File Walkthrough

	Relevant files
Configuration changes	releases.properties Add six new PostgreSQL versions with download URLs              releases.properties Added six new PostgreSQL version entries from release 2025.11.22 Versions added: 18.1, 17.7, 16.11, 15.15, 14.20, 13.23 Each entry includes download URL pointing to GitHub release assets Maintained descending semver ordering with newest versions first +6/-1

---

[qodo-code-review]

PR Compliance Guide 🔍

Below is a summary of compliance checks for this PR:

Security Compliance
🟢	No security concerns identified No security vulnerabilities detected by AI analysis. Human verification advised for critical code.
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

[github-actions]

🐘 PostgreSQL Module Tests - Results

Test Date: 2026-01-03 02:03:07 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 Code Suggestions ✨

Explore these optional code suggestions:

Category	Suggestion	Impact
Possible issue	Correct artifact URL suffix Update the artifact suffix in the new version URLs from -2025.7.2.7z to -2025.11.22.7z to match the release tag and ensure correct download links. releases.properties [1] -18.1 = 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.11.22.7z Apply / Chat Suggestion importance[1-10]: 9 __ Why: This suggestion correctly identifies a critical copy-paste error where the download URLs for new versions point to non-existent files, which would break the download functionality.	High
More