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

Safety fails for coverage versions before 6.0.0 #756

Closed
Zethson opened this issue Aug 3, 2021 · 3 comments
Closed

Safety fails for coverage versions before 6.0.0 #756

Zethson opened this issue Aug 3, 2021 · 3 comments
Assignees
Labels
bug Something isn't working

Comments

@Zethson
Copy link
Member

Zethson commented Aug 3, 2021

Safety fails for cli-python for coverage versions lower than 6.0.0.

6.0.0 must be released soon and we have to update the template.

@Zethson Zethson added the bug Something isn't working label Aug 3, 2021
@Zethson Zethson self-assigned this Aug 3, 2021
@Zethson
Copy link
Member Author

Zethson commented Aug 3, 2021

pyupio/safety-db#2335

@Zethson
Copy link
Member Author

Zethson commented Aug 3, 2021

Hi @whyscream, thanks for reporting this issue. We reviewed in detail and this was a false positive, we have marked the vulnerability as INVALID and the update will be available soon.

Ahh, whatever

@e2jk
Copy link
Contributor

e2jk commented Aug 3, 2021

I've had the same issue after creating my first project and uploading it to GitHub.
I've gotten around it by allowing coverage to be upgraded to it's available pre-release version that safety reports about.
See e2jk/timelog_tracker@7b2a5a2 for inspiration.

(I'm a bit surprised that safety would basically force us to upgrade to a pre-release version, when the comment indicates that coverage starting with version 6.0.0 will be using a better hashing algorithm...)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants