Update releases.properties from release 2026.4.16

[N6REJ]

🤖 Automated Releases Properties Update

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

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-mailpit/releases/tag/2026.4.16

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 Mailpit 1.29.7 release to properties

✨ Enhancement

Walkthroughs

Description

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

Diagram

flowchart LR
  A["Release 2026.4.16"] -- "Extract version 1.29.7" --> B["releases.properties"]
  B -- "Add entry at top" --> C["1.29.7 with download URL"]

Loading

File Changes

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

Add Mailpit 1.29.7 release entry

• Added new version entry 1.29.7 at the top of the file
• Included download URL pointing to release 2026.4.16
• Maintained semver ordering with newest version first
• Preserved all existing version entries unchanged

releases.properties

---

[qodo-code-review]

Code Review by Qodo

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

1. Mismatched release URL date 🐞 Bug ≡ Correctness

Description

The new 1.29.7 entry uses a release download path for tag 2026.4.16 but the asset filename embeds
2026.4.19, unlike the established pattern in this file. If the asset name follows the release tag
convention, the URL will not resolve and the link-validation workflow will fail on a non-200
response.

Code

releases.properties[4]

+1.29.7 = https://github.com/Bearsampp/module-mailpit/releases/download/2026.4.16/bearsampp-mailpit-1.29.7-2026.4.19.7z

Evidence

The new line introduces a mismatch between the GitHub release tag segment
(.../download/2026.4.16/) and the asset’s date suffix (...-2026.4.19.7z). Existing entries
consistently use the same date in both the tag and filename, and the CI workflow explicitly fails
validation for any URL that does not return HTTP 200.

releases.properties[4-7]
.github/workflows/validate-properties-links.yml[118-144]

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` has a new 1.29.7 mapping whose URL contains two different release identifiers:
- Download tag path uses `2026.4.16`
- Asset filename ends with `2026.4.19.7z`

This breaks the established convention in this repository and is likely to produce an invalid URL (causing the link validation workflow to fail).

### Issue Context
Other entries in `releases.properties` consistently match the download tag date with the asset filename date (e.g., `/download/2026.3.5/...-2026.3.5.7z`). The PR validation workflow performs HTTP requests and treats any non-200 response as a failure.

### Fix Focus Areas
- releases.properties[4-4]

### What to change
Update the 1.29.7 line so the download path tag and the asset filename correspond to the actual published asset for the intended release (likely change the filename suffix to `...-2026.4.16.7z`, unless the release tag/path should instead be `2026.4.19`).

ⓘ 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

[qodo-code-review]

1. Mismatched release url date 🐞 Bug ≡ Correctness

The new 1.29.7 entry uses a release download path for tag 2026.4.16 but the asset filename embeds
2026.4.19, unlike the established pattern in this file. If the asset name follows the release tag
convention, the URL will not resolve and the link-validation workflow will fail on a non-200
response.

Agent Prompt

### Issue description
`releases.properties` has a new 1.29.7 mapping whose URL contains two different release identifiers:
- Download tag path uses `2026.4.16`
- Asset filename ends with `2026.4.19.7z`

This breaks the established convention in this repository and is likely to produce an invalid URL (causing the link validation workflow to fail).

### Issue Context
Other entries in `releases.properties` consistently match the download tag date with the asset filename date (e.g., `/download/2026.3.5/...-2026.3.5.7z`). The PR validation workflow performs HTTP requests and treats any non-200 response as a failure.

### Fix Focus Areas
- releases.properties[4-4]

### What to change
Update the 1.29.7 line so the download path tag and the asset filename correspond to the actual published asset for the intended release (likely change the filename suffix to `...-2026.4.16.7z`, unless the release tag/path should instead be `2026.4.19`).

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