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

Seemingly accidental publish of version 2.4.2 makes npm miss out on 1.6.0+ #96

Open
FelixZY opened this issue May 3, 2024 · 5 comments

Comments

@FelixZY
Copy link

FelixZY commented May 3, 2024

npm lists version 1.7.1 of @unified-latex/unified-latex-prettier as the most recent release. However, looking at the dependency list for prettier-plugin-latex, version 2.4.2 is listed.

Indeed, version 2.4.2 is available on npmjs as an 8 month old release:

Screenshot from 2024-05-03 23-33-12

But it is not listed as a formal release on GitHub.

I'm assuming version 2.4.2 was pushed manually by accident. However, its presence on npmjs and listing in prettier-plugin-latex causes this version to be installed instead of actually newer releases such as 1.6.0+.

@siefkenj
Copy link
Owner

siefkenj commented May 3, 2024

Yes, that was a mistake. I have marked that version as deprecated. Hopefully that will solve the issue!

@FelixZY
Copy link
Author

FelixZY commented May 3, 2024

@siefkenj you probably want to fix the import in prettier-plugin-latex as well :)

Thank you for the quick response!

@FelixZY
Copy link
Author

FelixZY commented May 3, 2024

@siefkenj Attempting to install @unified-latex/unified-latex-prettier now produces a deprecation warning but still installs version 2.4.2:

$ npm i @unified-latex/unified-latex-prettier
npm WARN deprecated @unified-latex/unified-latex-prettier@2.4.2: Incorrect version number

added 213 packages, and audited 214 packages in 18s

58 packages are looking for funding
  run `npm fund` for details

found 0 vulnerabilities

@siefkenj
Copy link
Owner

siefkenj commented May 3, 2024

I'm not sure what else I can do. NPM doesn't let me unpublish...

@FelixZY
Copy link
Author

FelixZY commented May 3, 2024

You could bump the current version beyond 2.4.2. Not ideal but it's probably the best solution...

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