Latest Version Upgrade Error due to yarnpkg not Found 404

Command ghost update

Output :arrow_down:

+ sudo systemctl is-active ghost_groot-blog
✔ Checking system Node.js version
✔ Ensuring user is not logged in as ghost user
✔ Checking if logged in user is directory owner
✔ Checking current folder permissions
✔ Checking folder permissions
✔ Checking file permissions
✔ Checking content folder ownership
✔ Checking memory availability
✔ Checking for available migrations
✔ Checking for latest Ghost version
✖ Downloading and updating Ghost to v3.28.0
A ProcessError occurred.

Message: Command failed: yarn install --no-emoji --no-progress
warning ghost@3.28.0: The engine "cli" appears to be invalid.
warning Resolution field "moment@2.24.0" is incompatible with requested version "moment@2.25.1"
warning Resolution field "moment-timezone@0.5.23" is incompatible with requested version "moment-timezone@0.5.28"
warning Resolution field "moment@2.24.0" is incompatible with requested version "moment@2.27.0"
warning Resolution field "moment-timezone@0.5.23" is incompatible with requested version "moment-timezone@0.5.31"
error An unexpected error occurred: "https://registry.yarnpkg.com/@sentry/node/-/node-5.20.1.tgz: Request failed \"404 Not Found\"".

yarn install v1.22.4
[1/5] Validating package.json...
[2/5] Resolving packages...
[3/5] Fetching packages...
info If you think this is a bug, please open a bug report with the information provided in "/var/www/tmsblog/versions/3.28.0/yarn-error.log".
info Visit https://yarnpkg.com/en/docs/cli/install for documentation about this command.

Exit code: 1


Debug Information:
    OS: Ubuntu, v16.04.6 LTS
    Node Version: v12.18.3
    Ghost Version: 3.26.1
    Ghost-CLI Version: 1.14.1
    Environment: production
    Command: 'ghost update'

Additional log info available in: /home/groot/.ghost/logs/ghost-cli-debug-2020-08-06T11_03_11_116Z.log

Try running ghost doctor to check your system for known issues.

You can always refer to https://ghost.org/docs/api/ghost-cli/ for troubleshooting.

Hey @mskian! :wave:

It looks like NPM are having some issues with accessing scoped packages from them. It’s being tracked in an incident report here: https://status.npmjs.org/incidents/cksjqc1w11v5?u=yjqzk11ky282, but we hope for it to be resolved soon :slightly_smiling_face:

1 Like

Thanks for the Update