Update releases.properties from release 2026.1.5

[N6REJ]

User description

🤖 Automated Releases Properties Update

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

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.1.5

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

---

PR Type

Enhancement

---

Description

• Update PowerShell module version download URL

• Change release tag from 2025.11.30 to 2026.1.5

• Maintain version 7.5.4 with new release artifacts

---

Diagram Walkthrough

flowchart LR
  old["Release 2025.11.30"] -- "update to" --> new["Release 2026.1.5"]
  new -- "maintains" --> version["Version 7.5.4"]

Loading

File Walkthrough

	Relevant files
Configuration changes	releases.properties Update PowerShell release URL to 2026.1.5                                releases.properties Updated download URL for PowerShell version 7.5.4 Changed release tag from 2025.11.30 to 2026.1.5 Updated artifact filename to reflect new release date +1/-1

---

[qodo-code-review]

PR Compliance Guide 🔍

Below is a summary of compliance checks for this PR:

Security Compliance
⚪	Supply chain integrity Description: The updated entry points to a remotely hosted binary archive (.7z) without any accompanying integrity pinning (e.g., checksum/signature), which can enable supply-chain compromise if the upstream release asset or tag is tampered with. releases.properties [1-1] Referred Code 7.5.4 = https://github.com/Bearsampp/module-powershell/releases/download/2026.1.5/bearsampp-powershell-7.5.4-2026.1.5.7z
Ticket Compliance
⚪	🎫 No ticket provided Create ticket/issue
Codebase Duplication Compliance
⚪	Codebase context is not defined Follow the guide to enable codebase context checks.
Custom Compliance
🟢	Generic: Comprehensive Audit Trails Objective: To create a detailed and reliable record of critical system actions for security analysis and compliance. Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Meaningful Naming and Self-Documenting Code Objective: Ensure all identifiers clearly express their purpose and intent, making code self-documenting Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Robust Error Handling and Edge Case Management Objective: Ensure comprehensive error handling that provides meaningful context and graceful degradation Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Secure Error Handling Objective: To prevent the leakage of sensitive system information through error messages while providing sufficient detail for internal debugging. Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Secure Logging Practices Objective: To ensure logs are useful for debugging and auditing without exposing sensitive information like PII, PHI, or cardholder data. Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Security-First Input Validation and Data Handling Objective: Ensure all data inputs are validated, sanitized, and handled securely to prevent vulnerabilities Status: Passed Learn more about managing compliance generic rules or creating your own custom rules

Compliance status legend

🟢 - Fully Compliant
🟡 - Partial Compliant
🔴 - Not Compliant
⚪ - Requires Further Human Verification
🏷️ - Compliance label

[qodo-code-review]

PR Code Suggestions ✨

Explore these optional code suggestions:

Category	Suggestion	Impact
Possible issue	Correct inconsistent release tag date format The date format in the release tag 2026.1.5 is inconsistent with the previous format. Verify the correct tag on GitHub and consider using a zero-padded format (2026.01.05) to prevent potential download errors. releases.properties [1] -7.5.4 = https://github.com/Bearsampp/module-powershell/releases/download/2026.1.5/bearsampp-powershell-7.5.4-2026.1.5.7z +7.5.4 = https://github.com/Bearsampp/module-powershell/releases/download/2026.01.05/bearsampp-powershell-7.5.4-2026.01.05.7z Apply / Chat Suggestion importance[1-10]: 7 __ Why: The suggestion correctly identifies a potential functionality-breaking issue by pointing out the inconsistent date format in the URL, which could lead to download failures. It rightly advises verifying the tag to ensure correctness.	Medium
More