Skip to content

Conversation

anamnavi
Copy link
Member

@anamnavi anamnavi commented Aug 21, 2025

PR Summary

PowerShellGet v2 allowed for finding and installing unlisted versions of package, given that a full/non-wildcard name and a version were both specified. PSResourceGet changed this but fixing this to ensure backwards compatibility and provide support for requested scenarios. Scenarios include a team that may publish a module version, unlist it for consuming and testing it works as expected before making it listed again, or testing if a package version is unlisted and not missing altogether.

PR Context

Resolves #1771

PR Checklist

@anamnavi
Copy link
Member Author

/azp run

Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@anamnavi
Copy link
Member Author

/azp run

Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@anamnavi
Copy link
Member Author

/azp run

Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@anamnavi
Copy link
Member Author

/azp run

Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@anamnavi anamnavi merged commit d209bd2 into master Sep 4, 2025
12 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

'Find-PSResource' - Specifying exact name and version does not return an unlisted package (like 'Find-Module' does)

2 participants