Update releases.properties from release 2026.7.30

[N6REJ]

🤖 Automated Releases Properties Update

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

Changes:

• Extracted .7z assets from the release
• Removed stale/invalid existing URLs from releases.properties
• Added version entries with download URLs
• Maintained semver ordering (newest first)

Release URL: https://github.com/Bearsampp/module-powershell/releases/tag/2026.7.30

Next Steps:

1. ⏳ Link validation will run automatically
2. ✅ Once validation passes, this PR will auto-merge
3. ❌ If validation fails, review logs for transient network/service issues

[qodo-code-review]

PR Summary by Qodo

Add 7.6.4 download mapping to releases.properties (release 2026.7.30)

⚙️ Configuration changes 🕐 Less than 5 minutes

AI Description

• Add the 7.6.4 → GitHub release asset URL mapping for release 2026.7.30.
• Keep version entries ordered newest-first for deterministic resolution and review.

Diagram

graph TD
  A["GitHub Release 2026.7.30"] --> B["Update workflow"] --> C["releases.properties"] --> D["Gradle URL resolver"] --> E["Download/extract .7z"]
  C --> F["Link validation workflow"] --> G["Auto-merge gate"]

Loading

High-Level Assessment

This is the right approach for this repo: updating releases.properties keeps the build’s fallback URL resolution accurate and enables automated link validation/auto-merge. Alternatives (e.g., eliminating local releases.properties entirely) would require changing build assumptions and provide little benefit for this release-driven workflow.

Files changed (1) +1 / -0

Other (1) +1 / -0

releases.propertiesAdd 7.6.4 release URL entry +1/-0

Add 7.6.4 release URL entry

• Adds a new mapping for version 7.6.4 pointing to the 2026.7.30 GitHub release asset. The newest version remains at the top to preserve expected ordering.

releases.properties

[qodo-code-review]

Code Review by Qodo

🐞 Bugs (1) 📘 Rule violations (0) 📜 Skill insights (0)

1. Release suffix mismatch 🐞 Bug ⚙ Maintainability

Description

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.

Code

releases.properties[1]

+7.6.4 = https://github.com/Bearsampp/module-powershell/releases/download/2026.7.30/bearsampp-powershell-7.6.4-2026.6.25.7z

Evidence

The PR introduces the only entry where the release tag in the URL differs from the archive suffix.
The repo’s build configuration and documented artifact naming pattern use the release value as the
archive suffix, so the added mismatch is a new inconsistency that reduces traceability.

releases.properties[1-2]
build.properties[1-3]
build.gradle[1064-1072]
README.md[184-196]

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` 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

---

_{To customize comments, go to the Qodo configuration screen, or learn more in the docs.}

[qodo-code-review]

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