Skip to content

Update releases.properties from release 2026.7.30 #25

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
N6REJ merged 1 commit into from
Jul 30, 2026
Merged

Update releases.properties from release 2026.7.30 #25

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
1 change: 1 addition & 0 deletions releases.properties
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,3 +1,4 @@
7.6.4 = https://github.com/Bearsampp/module-powershell/releases/download/2026.7.30/bearsampp-powershell-7.6.4-2026.6.25.7z

@qodo-code-review qodo-code-review Bot Jul 30, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Remediation recommended

1. Release suffix mismatch 🐞 Bug ⚙ Maintainability

The new 7.6.4 mapping uses a download URL for release tag 2026.7.30, but the referenced archive
filename still ends with 2026.6.25. This introduces inconsistent release/build-date metadata versus
the repo’s own bundle.release-based naming and makes it unclear which release the artifact was built
for.
Agent Prompt 
### Issue description
`releases.properties` adds a 7.6.4 entry whose URL path indicates GitHub release tag `2026.7.30` while the asset filename suffix is `2026.6.25`. This makes the mapping’s release/build date inconsistent with the repository’s conventions.

### Issue Context
- Existing entries use the same date in both the `/download/<tag>/...` segment and the `...-<date>.7z` filename suffix.
- The repo’s build config (`bundle.release`) and output artifact naming include the release value as the archive suffix.

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

### Suggested fix
- Verify which suffix is correct for version `7.6.4`:
  - If the artifact for the `2026.7.30` release should be suffixed `2026.7.30`, update the URL to reference `bearsampp-powershell-7.6.4-2026.7.30.7z` (and ensure that asset exists in the release).
  - If the artifact is intentionally suffixed `2026.6.25`, consider publishing it under the matching release tag or documenting why the tag and artifact suffix differ.

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

7.6.3 = https://github.com/Bearsampp/module-powershell/releases/download/2026.6.25/bearsampp-powershell-7.6.3-2026.6.25.7z
7.6.2 = https://github.com/Bearsampp/module-powershell/releases/download/2026.6.25/bearsampp-powershell-7.6.2-2026.6.25.7z
7.6.1 = https://github.com/Bearsampp/module-powershell/releases/download/2026.6.25/bearsampp-powershell-7.6.1-2026.6.25.7z
Expand Down