Open tsondergaard opened 1 year ago
Seeing the same. Also, the critical vulnerability is probably an even bigger issue. @hassy
Thank you for the report! Can confirm, I'm able to reproduce it. We'll need to look into it. The behavior is odd as2.0.0-dev9
was never tagged as a latest
release and has been deprecated, but for some reason npm audit fix
must see it as the most recent version that satisfies some advisory in v2.0.0-28
.
Thanks, @hassy! Any ideas on the critical vulnerabilities? Would you like me to create a separate issue for that?
Still an issue with 2.0.0-33.
We've upgraded a bunch of dependencies recently (e.g. see #1971 and #1933). There are still a couple of dependencies that seem to be causing this issue, we're looking into it!
Is there any update on this issue?
Still an issue with 2.0.0-38.
I want to be able to run npm audit fix
on my project. I have opened a support case with npm support to see if they can do something in the registry to prevent downgrades to that old 2.0.0-dev9 version of artillery. If they report back with suggestions for something the artillery project needs to do I will add the information here.
Ah, I see it is already deprecated.
Version info:
Steps to reproduce:
Shell session running the commands above with some long irrelevant output replaced with ...:
I expected to see this happen: I expected
npm audit fix
to fix the problems.Instead, this happened:
npm audit fix
downgraded from from 2.0.0-28 to 2.0.0-dev9 which just has other/more issues. It seems to me that there is something screwed up with the version numbers sincenpm audit fix
considers it valid to move from 2.0.0-28 to 2.0.0-dev9.