Description
When browsing packages in the PowerShell Gallery, any main package page like https://www.powershellgallery.com/packages/ImportExcel/ will automatically redirect to a version-specific location for the most recently-released version, like https://www.powershellgallery.com/packages/ImportExcel/6.1.0.
If someone wants to link to this page in a blog post or stack overflow answer, they may copy this versioned link from their browser location bar and publish the version-specific link to the package instead of the generic link.
What then happens for any package that is undergoing continual development is that subsequent versions are released, and the published link to the package page is no longer directing new users to the "current" (aka "latest") version of the package.
The above may be grounds for a separate argument about whether redirecting the generic URL to a versioned one is a good idea in the first place, but for the moment I'd just like to take issue with the version annotation at the bottom of the package page.
Let's say you clicked a link in a blog post for https://www.powershellgallery.com/packages/ImportExcel/5.4.5. You now see something that looks like this:
The version of the package that you are accessing is annotated with "(current version)" in the version history. What this is trying to say is that you, the person browsing the website, are currently looking at the version indicated. This can be misleading because a user may interpret it to mean that the annotated version is the stable/production/supported version of the software at this time (i.e. "currently"), and that more recently-released versions are unstable or beta.
A less ambiguous alternative to "(current version)" in this context would be "(this version)". It's a better choice because "this" is true in the semantic context of the rest of the page content, and "current" is only true in the semantic context of the human reading the page, which sounds like it's probably an antipattern.