-
## The problem
Bumping from `@percy/cli 1.0.0-beta.76` to `1.0.0`, or `1.0.6`, is now causing every capture to redirect to the login view. We've been running this in a RoR's application for about 2…
-
## The problem
I'm attempting to upgrade to @percy/cli 1.0.0 (my CI logs told me a new version was available)
When I ran `npm install` I got the following
```bash
m ERR! command sh -c node .…
-
My team uses the `-c` parameter when running Storybook:
```sh
start-storybook -c ./configs/storybook --ci --port 9001
```
The command `percy storybook:start` does not allow me to configure thi…
-
## The problem
Can't change the port. The `-P` and `--port` arguments are ignored. The `PERCY_SERVER_PORT` environment variable is ignored.
## Environment
- Node version: `v16.14.0`
- `@perc…
-
From the readme:
>⚠️ This action is only required if you're using an older SDK not using Percy CLI. In Percy CLI, GitHub actions will work out of the box.
From the [docs](https://docs.percy.io/d…
-
### 1. Summary
**If** I installed md_mermaid package from GitHub branch via Pipenv:
Pipenv re-install this package every time when I install other packages.
In my opinion, this is undesirable b…
-
## The problem
Upon upgrading from "@percy/cypress": "^2.3.1" to "@percy/cypress": "^3.0.0", I found that "@percy/cli": "^1.0.0-beta.74" was added to my package.json by the instructions at https://…
-
## The problem
Upgrading the Percy CLI version broke my Jenkins build... Not sure why. To be honest, this is probably user error, but I thought I would drop it here anyways. Hopefully this will hel…
-
## The problem
After upgrading from `@percy/storybook": "^3.3.1` to `"@percy/cli": "^1.0.0-beta.73"`, `"@percy/storybook": "^4.1.0"` and running it on github hosted runner I encountered this error:…
-
## The problem
I've successfully run tests with Cypress and Percy locally, and am now trying to use [`browserstack-cypress-cli`](https://github.com/browserstack/browserstack-cypress-cli) to take…