Update releases.properties from release 2026.4.18

[N6REJ]

🤖 Automated Releases Properties Update

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

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-powershell/releases/tag/2026.4.18

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

Update PowerShell 7.6.0 release artifact version

✨ Enhancement

Walkthroughs

Description

• Updates PowerShell module version 7.6.0 download URL
• Corrects release artifact version from 2026.4.18 to 2026.4.24

Diagram

flowchart LR
  A["releases.properties"] -- "Update 7.6.0 artifact version" --> B["2026.4.24 release URL"]

Loading

File Changes

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

Update PowerShell 7.6.0 artifact version

• Updated version 7.6.0 download URL artifact version from 2026.4.18 to 2026.4.24
• Maintains semver ordering with existing entries

releases.properties

---

[qodo-code-review]

Code Review by Qodo

🐞 Bugs (1) 📘 Rule violations (0)

1. Mismatched tag vs filename 🐞 Bug ≡ Correctness

Description

releases.properties now maps 7.6.0 to a URL whose release tag segment is 2026.4.18 while the
asset filename embeds 2026.4.24, making the mapping internally inconsistent. If either the tag or
filename is wrong, Gradle’s releases.properties fallback path will attempt to download this URL
verbatim and fail at runtime when the remote asset is not found.

Code

releases.properties[1]

+7.6.0 = https://github.com/Bearsampp/module-powershell/releases/download/2026.4.18/bearsampp-powershell-7.6.0-2026.4.24.7z

Evidence

The modified mapping for 7.6.0 has a different release identifier in the
/releases/download/<tag>/...-<release>.7z components, unlike the documented convention where the
tag and filename release identifier match. The build script uses releases.properties as a direct
fallback source for the download URL and downloadFile() opens the URL stream directly (a
404/invalid URL will raise and fail the build).

releases.properties[1-2]
build.gradle[280-309]
build.gradle[152-193]
build.properties[1-4]
.gradle-docs/README.md[135-141]

Agent prompt

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

### Issue description
The `7.6.0` entry in `releases.properties` is internally inconsistent: the GitHub release tag segment is `2026.4.18` but the asset filename includes `2026.4.24`. This makes it unclear which release is intended and can cause a hard build failure if the URL does not exist.

### Issue Context
Gradle resolves version download URLs from `modules-untouched` first and falls back to `releases.properties`. The fallback URL is used verbatim, and `downloadFile()` opens the URL stream directly—so an incorrect URL will fail the build.

### Fix Focus Areas
- releases.properties[1-2]
- build.properties[1-4]

### What to change
1. Verify which GitHub release tag actually hosts the `bearsampp-powershell-7.6.0-*.7z` asset.
2. Update the `7.6.0` mapping so the `/releases/download/<tag>/` segment and the asset filename’s embedded release identifier refer to the same release (either update the tag to `2026.4.24` or revert the filename suffix to `2026.4.18`, whichever is correct).
3. Consider aligning the `7.5.4` entry as well if the intended release identifier is `2026.4.24`, to keep the file consistent.

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

---