search

percy / cli

The Percy CLI is used to interact with, and upload snapshots to, percy.io via the command line.
https://docs.percy.io/docs/cli-overview
70 stars 43 forks source link

Getting an error for @percy/cli-command when upgrading @percy/cli #978

Closed allypalanzi closed 2 years ago

allypalanzi commented 2 years ago

The problem

When trying to upgrade my node modules, I'm getting an issue where it cannot find version 1.5.1 of @percy/cli-command Screen Shot 2022-06-30 at 3 23 14 PM

I dont have this package manually installed, am only using it through @percy/cli

Environment

Details

If necessary, describe the problem you have been experiencing in more detail.

Debug logs

If you are reporting a bug, always include logs! Give the "Debugging SDKs" document a quick read for how to gather logs

Please do not trim or edit these logs, often times there are hints in the full logs that help debug what is going on.

Code to reproduce issue

Given the nature of testing/environment bugs, it’s best to try and isolate the issue in a reproducible repo. This will make it much easier for us to diagnose and fix.

Robdel12 commented 2 years ago

Hey @allypalanzi! I think there's something weird going on with NPM. The release workflow shows all the packages were released without any issues: https://github.com/percy/cli/runs/7138220134?check_suite_focus=true#step:6:249

NPM on the package list shows 1.5.1, but clicking it goes to 1.5.0 and also errors on 1.5.1. So something is really funky

image

I think I'm going to wait to see if there's anything that needs to propagate before trying to republish/release another version.

andyasberry commented 2 years ago

I had this issue also - looks like npm is having some issues right now related to this. I'll probably roll back to 1.5.0 for now.

Screen Shot 2022-06-30 at 4 05 30 PM

allypalanzi commented 2 years ago

thanks all, i'll close this. i had checked the NPM status page but it didnt have anything there yet!

Robdel12 commented 2 years ago

We're on the cutting edge! 😅 For record keeping, this is the status page for it: https://status.npmjs.org/incidents/6wr25yb0b2dd

Once that's resolved I'll double back to make sure we don't have rerelease or anything. Thanks for the report!

Robdel12 commented 2 years ago

👋🏼 It appears this has been back filled and resolved by NPM (I'm able to upgrade to the latest in my reproduction projects)