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

package.json uses old version #49

Closed
lil5 opened this issue Nov 4, 2018 · 4 comments
Closed

package.json uses old version #49

lil5 opened this issue Nov 4, 2018 · 4 comments

Comments

@lil5
Copy link
Contributor

lil5 commented Nov 4, 2018

No description provided.

@lil5
Copy link
Contributor Author

lil5 commented Nov 4, 2018

This could be fixed at pr #48 see #48 (comment)

@lil5
Copy link
Contributor Author

lil5 commented Nov 13, 2018

peer-calls - npm - https://www.npmjs.com/package/peer-calls

Shows 2.0.6 while package.json still 2.0.5

@lil5
Copy link
Contributor Author

lil5 commented Nov 14, 2018

I advice using --tag beta before publishing to stable. Npm doesn't allow version rewrites.

Fails if the package name and version combination already exists in the specified registry.

Once a package is published with a given name and version, that specific name and version combination can never be used again, even if it is removed with npm-unpublish.

@jeremija
Copy link
Member

jeremija commented Nov 14, 2018

This is my bad. I think I published a package before pushing to GitHub, and then I realized you've done all that work already so I didn't want to discredit your pull request. Will tag a new version as 2.0.7.

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