We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
pnpm-lock.yaml
The parsing of pnpm lockfiles can sometimes result in incorrect versions.
Steps to reproduce this behavior: I will provide a sample file in slack.
Correctly parse pnpm lockfiles.
Entries in the lockfile like this seem to be the cause:
The parser returns this:
But the correct version is just 1.2.2
1.2.2
The text was updated successfully, but these errors were encountered:
Fix PNPM v5 version parsing
6ae64a8
This fixes an issue with the lockfile parser of PNPM v5 lockfiles which would incorrectly include metadata in the package version. Closes #1538.
4c4246a
ff50531
cd-work
Successfully merging a pull request may close this issue.
Overview
The parsing of pnpm lockfiles can sometimes result in incorrect versions.
How To Reproduce
Steps to reproduce this behavior:
I will provide a sample file in slack.
Expected Behavior
Correctly parse pnpm lockfiles.
Additional Context
Entries in the lockfile like this seem to be the cause:
The parser returns this:
But the correct version is just
1.2.2
The text was updated successfully, but these errors were encountered: