-
Notifications
You must be signed in to change notification settings - Fork 468
Modifies latest-allowed to only match stable versions #439
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
base: master
Are you sure you want to change the base?
Conversation
|
cant it just fix it so Note I'm not a maintainer on this repo, just chanced upon this same issue Edit: |
|
@grillba you can use |
It is possible to fix the |
|
I think I am inclined to agree. latest-allowed and latest should be common. If latest matches only stable, latest-allowed probably should too. |
…nly behavior into `latest-allowed`, updating documentation and tests.
latest-allowed to only match stable versions
latest-allowed to only match stable versions|
@Zordrak I updated the |
Description
In the current implementation, the
latestandlatest-allowedoptions have potentially confusing behaviours:latest-allowedcan unexpectedly include pre-release versionslatestis limited to stable versions onlyThis discrepancy can cause issues, particularly in CI/CD pipelines where version predictability is crucial.
This PR is fixing that difference in the behaviours and makes sure the
latest-allowedonly finds stable versions.