Update releases.properties from release 2026.6.2

[N6REJ]

🤖 Automated Releases Properties Update

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

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

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.42 release to properties file

✨ Enhancement

Walkthroughs

Description

• Add memcached version 1.6.42 release entry
• Update releases.properties with new download URL
• Maintain semver ordering with newest version first

Diagram

flowchart LR
  release["Release 2026.6.2"] -- "Extract version 1.6.42" --> newEntry["New Entry: 1.6.42"]
  newEntry -- "Add to top of file" --> properties["releases.properties"]
  properties -- "Maintain semver order" --> ordered["Ordered: 1.6.42, 1.6.41, 1.6.40.7..."]

Loading

File Changes

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

Add memcached 1.6.42 release entry

• Added new version entry 1.6.42 at the top of the file
• Linked to release 2026.6.2 download URL
• Maintained semantic versioning order with newest version first

releases.properties

---

[qodo-code-review]

Code Review by Qodo

🐞 Bugs (1) 📘 Rule violations (0)

1. Docs format mismatch 🐞 Bug ⚙ Maintainability

Description

Repository docs describe releases.properties as date-keyed release-history text, but the file
(including the newly added 1.6.42 entry) is actually a version->download URL mapping written by the
update workflow. This mismatch can cause maintainers to edit the file using the wrong format and
break/complicate automation and link validation expectations.

Code

releases.properties[1]

Evidence

The documentation defines releases.properties as date-based release history, while both the
automation and the actual file content use version keys mapped to GitHub download URLs; the new
entry follows the version->URL pattern, reinforcing the mismatch.

.gradle-docs/CONFIGURATION.md[199-216]
.github/workflows/update-releases-properties.yml[156-252]
releases.properties[1-4]

Agent prompt

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

## Issue description
`releases.properties` is documented as a date-keyed “release history” file, but in this repo it is used as a `moduleVersion = downloadUrl` mapping and is maintained by the `update-releases-properties` GitHub workflow.

## Issue Context
- The automation parses property keys as versions and writes URL values.
- The documentation example currently shows date keys and human text values.

## Fix Focus Areas
- .gradle-docs/CONFIGURATION.md[199-216]
- .github/workflows/update-releases-properties.yml[156-252]
- releases.properties[1-4]

## Suggested fix
- Update `.gradle-docs/CONFIGURATION.md` (and any other docs referencing the file) to describe the real format: `memcached_version = GitHub_release_asset_url` (newest version first).
- Optionally add a short header comment at the top of `releases.properties` (e.g., `# Memcached version -> GitHub asset URL`) to prevent manual-format mistakes.

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

---