Update releases.properties from release 2026.3.7

[N6REJ]

🤖 Automated Releases Properties Update

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

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-memcached/releases/tag/2026.3.7

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 memcached 1.6.41 to releases.properties

✨ Enhancement

Walkthroughs

Description

• Add memcached version 1.6.41 from release 2026.3.7
• Update releases.properties with new download URL
• Maintain semver ordering with newest version first

Diagram

flowchart LR
  release["Release 2026.3.7"]
  extract["Extract .7z asset"]
  update["Update releases.properties"]
  version["Add version 1.6.41"]
  
  release -- "contains" --> extract
  extract -- "generates" --> version
  version -- "adds to" --> update

Loading

File Changes

1. releases.properties ⚙️ Configuration changes +1/-0

Add memcached 1.6.41 version entry

• Added new version entry 1.6.41 at the top of the file
• Linked to download URL from release 2026.3.7
• Maintained semver ordering with newest version first
• All existing version entries preserved

releases.properties

---

[qodo-code-review]

Code Review by Qodo

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

1. Docs mismatch for releases.properties 🐞 Bug ✓ Correctness

Description

Repo documentation presents releases.properties as a date→description “release history” file, but
the real file (including the new entry) is version→download-URL. This can mislead
maintainers/automation changes and increase the chance of future incorrect updates.

Code

releases.properties[1]

+1.6.41 = https://github.com/Bearsampp/module-memcached/releases/download/2026.3.7/bearsampp-memcached-1.6.41-2026.3.7.7z

Evidence

The updated releases.properties clearly maps module versions to GitHub release asset URLs, while
the docs describe and exemplify a different key/value meaning (dates mapped to descriptive text).

releases.properties[1-4]
.gradle-docs/CONFIGURATION.md[197-216]

Agent prompt

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

### Issue description
`.gradle-docs/CONFIGURATION.md` documents `releases.properties` as date→description release history metadata, but in this repository it is actually used as version→download-URL mapping. This mismatch can cause confusion and incorrect future updates.

### Issue Context
The PR adds a new entry to `releases.properties`, reinforcing the current real-world format (version = URL). The docs should reflect this.

### Fix Focus Areas
- .gradle-docs/CONFIGURATION.md[197-216]
- releases.properties[1-4]

ⓘ 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