Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

#

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Jump to bottom

4.0.0 is not published to npm #1721

Closed
limonte opened this issue Apr 17, 2019 · 6 comments
Closed

4.0.0 is not published to npm #1721

limonte opened this issue Apr 17, 2019 · 6 comments

Comments

@limonte
Copy link

limonte commented Apr 17, 2019

https://github.com/nodejs/node-gyp/blob/master/package.json#L14

image

https://www.npmjs.com/package/node-gyp

image

Expected: 4.0.0 is published to npm
@limonte
Copy link
Author

limonte commented Apr 17, 2019 •
edited
Loading

hm, 75cfae2

The bump to v4.0.0 happened 2 years ago, but 4.0.0 was never published to npm.

I have no idea what is happening with releasing of this package, can someone explain this mystery?

@limonte
Copy link
Author

limonte commented Apr 17, 2019 •
edited
Loading

this issue results into node-gyp being vulnerable:

image

@limonte limonte mentioned this issue Apr 17, 2019
Merged
limonte referenced this issue Apr 17, 2019
@refack
bump to v4.0.0
75cfae2 
* dropping support for node < 4
* signal the CI not to test node < 4
@JCMais
Copy link

JCMais commented Apr 17, 2019 •
edited
Loading

Related to #1717

cc @nodejs/node-gyp

@JoshRobertson JoshRobertson mentioned this issue Apr 17, 2019
Closed
jhnferraris referenced this issue Apr 18, 2019
@MaksPob @refack
deps: updated tar package version to 4.4.8
1456ef2 
PR-URL: #1713
Reviewed-By: Refael Ackermann <refack@gmail.com>
@shehi
Copy link

shehi commented Apr 19, 2019

@limonte , this situation will be remedied?

@limonte
Copy link
Author

limonte commented Apr 19, 2019

@shehi I'm not the maintainer of this package. 2 years wasn't enough to run npm publish so I'd assume we'll need to wait a few more years.

@limonte limonte mentioned this issue Apr 22, 2019
Merged
@rhanka rhanka mentioned this issue Apr 22, 2019
Merged
@cclauss cclauss mentioned this issue Apr 24, 2019
Closed
@ChALkeR
Copy link
Member

ChALkeR commented Apr 24, 2019 •
edited
Loading

I think this is now fixed per #1718 (comment) (thanks, @rvagg!).

Closing this now, feel free to reopen and/or comment though.

$ npm i node-gyp
+ node-gyp@4.0.0
added 100 packages from 67 contributors and audited 156 packages in 5.265s
found 0 vulnerabilities

@ChALkeR ChALkeR closed this as completed Apr 24, 2019
# for free to join this conversation on GitHub. Already have an account? # to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@ChALkeR @shehi @JCMais @limonte