-
-
Notifications
You must be signed in to change notification settings - Fork 1.4k
Closed
Labels
Description
Verify latest release
- I verified that the issue exists in the latest pnpm release
pnpm version
No response
Which area(s) of pnpm are affected? (leave empty if unsure)
Lockfile
Link to the code that reproduces this issue or a replay of the bug
No response
Reproduction steps
Describe the Bug
After running these commands:
corepack use pnpm@latest
# Done in 1.1s using pnpm v10.31.0
pnpm updatethe tarball section is stripped from pnpm-lock.yaml:
'@jsr/std__collections@1.1.6':
- resolution: {integrity: sha512-hmuIU7r/xepXLXIBiK9gmq1BnSalyySnfdJ1mqvT39hU2g4Pz0DJDx6z1CMWVGbUQhpxBHuVQH9diqwMoN6/pw==, tarball: https://npm.jsr.io/~/11/@jsr/std__collections/1.1.6.tgz}
+ resolution: {integrity: sha512-hmuIU7r/xepXLXIBiK9gmq1BnSalyySnfdJ1mqvT39hU2g4Pz0DJDx6z1CMWVGbUQhpxBHuVQH9diqwMoN6/pw==}causing this installation issue:
16:05:52.926 | ERR_PNPM_FETCH_404 GET https://npm.jsr.io/@jsr/std__front-matter/-/std__front-matter-1.0.9.tgz: Not Found - 404
-- | --
16:05:52.926 |
16:05:52.927 | No authorization header was set for the request.
Expected Behavior
Lockfile installation should work.
Which Node.js version are you using?
v24.14.0
Which operating systems have you used?
- macOS
- Windows
- Linux
If your OS is a Linux based, which one it is? (Include the version if relevant)
No response
Reactions are currently unavailable