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
Update fail to compare version using git #7415
Comments
@KSXGitHub can you tell us more about your linux machine ? I just try on another windows machine (not clean / I use it to developp too, so maybe a common configuration problem), and got the same problem . But I also tryed on WSL, and got the nearly same error :
( If I have some time, I will setup the debugger to check more on this error ) |
@thib3113 I just cloned your repo and run it. Is that the right step? I noticed that the root |
@KSXGitHub did you have install dependencies before ?
Else, what is your linux distribution ? ( because, seems strange that it works on linux, but not on wsl debian 11) |
@thib3113 I see. The error has been reproduced. |
I have located the cause of the error to be at a pnpm/reviewing/outdated/src/outdated.ts Line 148 in 81e5ada
Your desired behavior is quite complex to implement right now, so I'll probably fix this error by ignoring non-semver values of |
@KSXGitHub I understand, no problem . maybe you can just ask if the person want to update ? without comparing value with next one ? and so we can check or not to do the update ? |
Actually, it was caused by pnpm/reviewing/outdated/src/outdated.ts Line 112 in 81e5ada
The true fix turns out to be more complicated than I initially thought. |
Verify latest release
pnpm version
8.12.1
Which area(s) of pnpm are affected? (leave empty if unsure)
No response
Link to the code that reproduces this issue or a replay of the bug
https://github.com/thib3113/pnpm-issue-7415
In this repos, need to do (I already add overrides) :
Reproduction steps
p update -r --latest -i
(without -r or -i seems to doesn't reproduce the bug)Describe the Bug
pnpm seems to try to compare the "github version" (as stored in the lockFile), with another version using semver
Expected Behavior
other way to check git repository (not with semver ? but by git hash ?)
Which Node.js version are you using?
20.8.0
Which operating systems have you used?
The text was updated successfully, but these errors were encountered: