Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

API - Some packages are not returned if semverlevel=2.0.0, but are returned if semverlevel=1.0.0 #268

Open
3 tasks done
o-l-a-v opened this issue Mar 24, 2024 · 0 comments

Comments

@o-l-a-v
Copy link

o-l-a-v commented Mar 24, 2024

Prerequisites

  • Write a descriptive title.
  • Make sure you are able to repro it on the latest version
  • Search the existing issues.

Steps to reproduce

Found two modules that the PowerShell Gallery API won't return if semverlevel=2.0.0, but does return if semverlevel=1.0.0.

  • PoshRSJob
  • PolicyFileEditor

Query that works:

Query that doesn't:

Observation: If you don't filter IsLatestVersion and not IsPrerelease, semverlevel=2.0.0 seems to work just fine:

Also if you only filter IsLatestVersion (but this returns preview versions if that's the newest one available. Which might be another issue, shouldn't only IsAbsoluteLatestVersion trigger that?):

Expected behavior

SemVerLevel shouldn't affect whether the package was found.

Actual behavior

SemVerLevel affects whether the package was found.

Error details

No response

Environment data

Not relevant, API.

Version

Not relevant, API.

Visuals

No response

@o-l-a-v o-l-a-v changed the title Some packages are not returned if semverlevel=2.0.0, returned if semverlevel=1.0.0 API - Some packages are not returned if semverlevel=2.0.0, but are returned if semverlevel=1.0.0 Mar 24, 2024
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

No branches or pull requests

1 participant