Fix PowerShell Gallery preview badge

[PrzemyslawKlys]

Shields changed the PowerShell Gallery prerelease badge endpoint and the old vpre badge now renders a placeholder link.

This updates README badge URLs to use the normal PowerShell Gallery version badge with include_prereleases, so it displays the prerelease version again.

Ref: badges/shields#11583

[chatgpt-codex-connector]

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.
To continue using code reviews, add credits to your account and enable them for code reviews in your settings.

[claude]

Claude finished @PrzemyslawKlys's task —— View job

---

PR Review: Fix PowerShell Gallery preview badge

Review Checklist:

• Read and analyze the changed README.md file
• Verify the badge URL modification is correct
• Check for potential issues or improvements
• Provide comprehensive review feedback

Analysis

Change Summary:
The PR updates line 8 in README.md, changing the PowerShell Gallery preview badge URL from:

https://img.shields.io/powershellgallery/vpre/PSEventViewer.svg?label=powershell%20gallery%20preview&colorB=yellow

to:

https://img.shields.io/powershellgallery/v/PSEventViewer.svg?label=powershell%20gallery%20preview&colorB=yellow&include_prereleases

Review Feedback

✅ Code Quality & Best Practices

• Excellent: The change is minimal, focused, and addresses exactly the issue described
• Proper documentation: Clear PR description with reference to the upstream Shields.io issue
• Consistent styling: Maintains the same URL structure and parameters as the existing badge

✅ Correctness & Functionality

• Accurate fix: The change correctly replaces the deprecated /vpre/ endpoint with /v/ + include_prereleases parameter
• Preserves behavior: The new URL will continue to show prerelease versions as intended
• Valid syntax: The URL parameters are properly formatted and escaped

✅ Performance & Security

• No performance impact: Badge URLs are loaded by browsers, no impact on the codebase
• No security concerns: Using official Shields.io endpoints with standard parameters
• Reliable service: Shields.io is a well-established service for repository badges

✅ Maintenance & Future-proofing

• Forward compatible: Using the current Shields.io API as recommended by their team
• Reference tracking: PR includes link to upstream issue for future maintainers
• Standard approach: The include_prereleases parameter is the recommended way to show prereleases

💡 Minor Suggestions

• Consider adding a comment in the README or documentation about the badge change rationale (optional)
• The change is already well-documented in the git history and PR description

🔍 Test Coverage

• N/A for this change: Badge URLs are external resources that don't require unit tests
• Manual verification: The badge should render correctly in the README when viewed on GitHub

Conclusion

This is an excellent, focused fix that addresses the Shields.io API deprecation. The change is minimal, correct, and well-documented. The PR maintains functionality while using the recommended modern API endpoint.

Recommendation: ✅ APPROVE - Ready to merge without any concerns.

---