Update memcached properties from release memcached-2026.03.07

[N6REJ]

🤖 Automated Module Properties Update

This PR updates the memcached.properties file with new versions from release memcached-2026.03.07.

Changes:

• Extracted assets starting with memcached (.7z, .exe, or .zip files)
• Added version entries with download URLs
• Maintained semver ordering (newest first)

Release URL: https://github.com/Bearsampp/modules-untouched/releases/tag/memcached-2026.03.07

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 module properties

✨ Enhancement

Walkthroughs

Description

• Add memcached version 1.6.41 with download URL
• Maintain semver ordering with newest version first
• Update module properties from release memcached-2026.03.07

Diagram

flowchart LR
  A["memcached-2026.03.07 Release"] -- "Extract version 1.6.41" --> B["Add to memcached.properties"]
  B -- "Maintain semver order" --> C["1.6.41 at top of list"]

Loading

File Changes

1. modules/memcached.properties ✨ Enhancement +1/-0

Add memcached 1.6.41 version entry

• Added new version entry 1.6.41 with download URL from memcached-2026.03.07 release
• Positioned at top of file maintaining semver ordering (newest first)
• Download URL points to GitHub Bearsampp modules-untouched release

modules/memcached.properties

---

[qodo-code-review]

Code Review by Qodo

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

1. Memcached key/filename mismatch 🐞 Bug ✓ Correctness

Description

modules/memcached.properties includes a 1.6.40.7 entry whose URL points to an asset named
memcached-1.6.40.7z. The repo’s update automation extracts versions from filenames in a way that
would parse that filename as 1.6.40 (not 1.6.40.7), risking future duplicate keys and ambiguity
for version selection.

Code

modules/memcached.properties[R1-2]

+1.6.41 = https://github.com/Bearsampp/modules-untouched/releases/download/memcached-2026.03.07/memcached-1.6.41.7z
1.6.40.7 = https://github.com/Bearsampp/modules-untouched/releases/download/Memcached-2026.1.15/memcached-1.6.40.7z

Evidence

The properties file key 1.6.40.7 does not obviously correspond to the referenced asset name
memcached-1.6.40.7z. The update workflow’s generic module handler extracts versions using a regex
that stops before the .7z extension, so it would extract 1.6.40 from memcached-1.6.40.7z, not
1.6.40.7. That means future automated runs could add a new 1.6.40 entry (duplicate semantics)
instead of updating/recognizing the existing 1.6.40.7 key.

modules/memcached.properties[1-2]
.github/workflows/update-module-properties.yml[382-399]

Agent prompt

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

### Issue description
`modules/memcached.properties` has an entry keyed as `1.6.40.7` but pointing at an asset named `memcached-1.6.40.7z`. Our update workflow’s generic version extraction would parse that filename as `1.6.40`, which can cause future automated updates to create a separate `1.6.40` key and make version selection ambiguous.

### Issue Context
The automation extracts versions from asset filenames via regex for standard modules; for `.7z` assets it intentionally avoids treating the `7` in `.7z` as part of the version.

### Fix Focus Areas
- modules/memcached.properties[1-4]
- .github/workflows/update-module-properties.yml[382-399]

ⓘ 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