Skip to content
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 1 addition & 2 deletions releases.properties
Original file line number Diff line number Diff line change
@@ -1,3 +1,2 @@
7.6.1 = https://github.com/Bearsampp/module-powershell/releases/download/2026.4.24/bearsampp-powershell-7.6.1-2026.4.24.7z
7.6.0 = https://github.com/Bearsampp/module-powershell/releases/download/2026.4.18/bearsampp-powershell-7.6.0-2026.4.18.7z
7.5.4 = https://github.com/Bearsampp/module-powershell/releases/download/2026.4.18/bearsampp-powershell-7.5.4-2026.4.18.7z
7.5.4 = https://github.com/Bearsampp/module-powershell/releases/download/2026.4.18/bearsampp-powershell-7.5.4-2026.4.24.7z
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Action required

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

Loading