We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Depending on a discontinued package is not healthy for the ecosystem in the long run
It could be seen as equivalent to not allowing the latest version of a dependency in your constraint.
cc @kevmoo @mit-mit
The text was updated successfully, but these errors were encountered:
I'm not sure about this. It's possible for a package to be marked as "discontinued" and still be fully functional.
Sorry, something went wrong.
(opinions:)
While this is true, it is not healthy in the long run.
Several things are potentially fully functional (such as having false positive warnings, not allowing the latest version of a dependency),
We still want package authors to react to these and move the ecosystem forwards.
Successfully merging a pull request may close this issue.
Depending on a discontinued package is not healthy for the ecosystem in the long run
It could be seen as equivalent to not allowing the latest version of a dependency in your constraint.
cc @kevmoo @mit-mit
The text was updated successfully, but these errors were encountered: