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

Code in repo is older than on npm? #72

Closed
watson opened this issue Jul 24, 2018 · 3 comments
Closed

Code in repo is older than on npm? #72

watson opened this issue Jul 24, 2018 · 3 comments

Comments

@watson
Copy link

watson commented Jul 24, 2018

FYI: The latest version in this repo is version 2.0.12, but according to https://www.npmjs.com/package/pidusage version 2.0.13 and 2.0.14 have also been released?

But at the same time new commits have been added to master after those two versions have been released, so I fear something is getting out of sync and just wanted you give you a heads up 😃

@watson
Copy link
Author

watson commented Jul 24, 2018

I just took a second look on npm and it seems that you have two versions of repo that is used to publish to npm and those two versions are not in sync. Notice how version 2.0.11 was released first, then 2.0.13, then 2.0.12, and then 2.0.14:

image

@soyuka
Copy link
Owner

soyuka commented Jul 24, 2018

I have indeed a really weird issue with npm, I don't get why it published this bugged version. pidusage@2.0.14 should be fine.

@soyuka
Copy link
Owner

soyuka commented Jul 24, 2018

Wow 2.0.14 is the one I published with only a lockfile, 2.0.13 was just fine and I never published the code between 737fdb7 and 1e590b2 really sorry about this!

2.0.15 is good, 2.0.14 has been unpublished

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants