Richie Ho

what can we do to get around this? what is the optimum viewport for both open and run to match?

   I was missing a label ('released'). Re-ran the build, and problem still persists.

my `.autorc` file: ``` json { "owner": "xxx", "repo": "xxx", "name": "xxx", "email": "xxx", "githubApi": "https://xxx.xxx.com/api/v3", "githubGraphqlApi": "https://xxx.xxx.com/api", "plugins": ["released"] } ``` my custom CI script to do releasing: ```...

> Is that a log from `shipit` I have a feeling this is because you aren't using the npm plugin and as a result I don't think you are properly...

> Only the `shipit` command will do that. since you switched to the manual setup you would need to run `npm publish` as well. > > But I think if...

I tried a few more things: - removed the following: still didn't work - ``` - git remote set-url origin https://xxx - git checkout master - git config --global user.email...

@hipstersmoothie I've replicated the issue on a public repo here: https://github.com/RichieRunner/node-test/releases I don't use CircleCI, so you'll have to create a CircleCI build to test. (I'm beginning to suspect that...

My research has led me to understand that I should be instrumenting code coverage through build, but I've now stumbled onto a new issue, which is [this one](https://github.com/cypress-io/instrument-cra/issues/212)

Bump on this issue. @TomaszG have you been able to resolve this? This pathing issue is causing my NP builds to not work in CI environments. I guess this instrumentation...

It has been 10 months, when is this going to be fixed? Even `Enabled: False` doesn't even work anymore.