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 module releases.properties file

✨ Enhancement

Walkthroughs

Description

• Updates PowerShell module version 7.5.4 download URL
• Changes release tag from 2026.4.18 to 2026.4.24
• Removes outdated version 7.6.1 entry

Diagram

flowchart LR
  old["7.5.4 with 2026.4.18"] -- "update to 2026.4.24" --> new["7.5.4 with 2026.4.24"]
  removed["7.6.1 entry"] -- "removed" --> deleted["deleted"]

Loading

File Changes

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

Update PowerShell module version URLs

• Updated version 7.5.4 download URL to use release tag 2026.4.24 instead of 2026.4.18
• Removed outdated version 7.6.1 entry
• Maintained version 7.6.0 with original 2026.4.18 release tag

releases.properties

---

[qodo-code-review]

Code Review by Qodo

🐞 Bugs (2) 📘 Rule violations (0)

1. Broken 7.5.4 URL 🐞 Bug ≡ Correctness

Description

The 7.5.4 entry points to a 2026.4.18 release tag but an asset filename containing 2026.4.24, making
the URL inconsistent and likely non-existent. When Gradle falls back to releases.properties, this
will fail at download time and break the build for 7.5.4.

Code

releases.properties[2]

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

Evidence

The updated mapping for 7.5.4 mixes release identifiers (tag 2026.4.18 vs filename 2026.4.24). The
build’s fallback resolver reads releases.properties and then downloadFile() immediately opens the
URL stream (no graceful handling for 404), so an invalid URL will surface as a hard build failure
when that fallback path is used.

releases.properties[1-2]
build.gradle[280-309]
build.gradle[152-170]

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` maps version `7.5.4` to a URL whose download tag (`2026.4.18`) does not match the asset filename suffix (`2026.4.24`). This is likely an invalid URL and can break builds when the Gradle fallback uses `releases.properties`.

### Issue Context
Gradle reads `releases.properties` as a fallback URL source and then downloads via `downloadFile()`, which opens the URL stream directly.

### Fix Focus Areas
- releases.properties[2-2]
- build.gradle[294-305]
- build.gradle[152-170]

### Expected change
Update the `7.5.4` value so the `{tag}` and `{filename}` refer to the same real release asset (most likely change the filename portion to `...-2026.4.18.7z`, or adjust the tag if the asset is actually under `2026.4.24`).

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

---

2. Missing 7.6.1 URL 🐞 Bug ☼ Reliability

Description

The 7.6.1 mapping was removed from releases.properties even though the repository contains a 7.6.1
version directory and the build enumerates and builds all bin/ versions. If the build falls back to
releases.properties (e.g., modules-untouched properties fetch fails), 7.6.1 will no longer resolve
to the known-good URL.

Code

releases.properties[1]

-7.6.1 = https://github.com/Bearsampp/module-powershell/releases/download/2026.4.24/bearsampp-powershell-7.6.1-2026.4.24.7z

Evidence

The repo still includes configuration for PowerShell 7.6.1, and the Gradle build’s releaseAll task
builds all versions discovered under bin/. URL resolution explicitly falls back to
releases.properties; removing the 7.6.1 key eliminates the local fallback mapping for a version
the build will attempt to process.

bin/powershell7.6.1/bearsampp.conf[1-3]
build.gradle[83-106]
build.gradle[1238-1275]
build.gradle[294-309]

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` no longer contains an entry for version `7.6.1`, but the build enumerates versions from `bin/` and will attempt to build/download for `7.6.1`.

### Issue Context
`downloadFromModulesUntouched()` explicitly uses `releases.properties` as a fallback URL source. Removing the `7.6.1` key reduces resilience when the primary source (modules-untouched properties) is unavailable or missing that version.

### Fix Focus Areas
- releases.properties[1-2]
- build.gradle[83-106]
- build.gradle[1238-1275]
- build.gradle[294-309]

### Expected change
Re-add the removed `7.6.1 = ...` line (with the correct, existing asset URL) so local fallback resolution continues to work for all versions present under `bin/`.

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

---

[qodo-code-review]

1. Broken 7.5.4 url 🐞 Bug ≡ Correctness

The 7.5.4 entry points to a 2026.4.18 release tag but an asset filename containing 2026.4.24, making
the URL inconsistent and likely non-existent. When Gradle falls back to releases.properties, this
will fail at download time and break the build for 7.5.4.

Agent Prompt

### Issue description
`releases.properties` maps version `7.5.4` to a URL whose download tag (`2026.4.18`) does not match the asset filename suffix (`2026.4.24`). This is likely an invalid URL and can break builds when the Gradle fallback uses `releases.properties`.

### Issue Context
Gradle reads `releases.properties` as a fallback URL source and then downloads via `downloadFile()`, which opens the URL stream directly.

### Fix Focus Areas
- releases.properties[2-2]
- build.gradle[294-305]
- build.gradle[152-170]

### Expected change
Update the `7.5.4` value so the `{tag}` and `{filename}` refer to the same real release asset (most likely change the filename portion to `...-2026.4.18.7z`, or adjust the tag if the asset is actually under `2026.4.24`).

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