-
-
Notifications
You must be signed in to change notification settings - Fork 36
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
Alamofire Shows No Info For Dependencies #2873
Comments
Thanks for the report, @jshier . This seems to have corrected itself in the meantime: I believe what's happening is that this reverts to "no information" when we detect a change on the default branch until the compatibility build with new dependency information is complete. We should try and preserve the original data in this case. |
hah, we must have both been replying at the same time 😂 |
This would be good, but I think there may be another good change to make here. We should calculate the score (and this score report) slightly differently. We currently base it on the default branch, but we should base it on the stable release, or if it does not have one, a pre-release, and only of both of those don't exist then the default branch. We have this logic encoded in lots of places in the app, so it shouldn't be a big change. Tracked in #2874 |
Which package(s) are showing incorrect data?
Please explain what data is incorrect and what you expected to see
According to the Package Score section, there is info for dependencies. Alamofire has no dependencies, and there is nothing in the package.
Screenshots
Additional context
Discussed with Dave offline, suggested reporting a bug.
The text was updated successfully, but these errors were encountered: