Gareth Jones

@serhalp can this be landed and released so we can have it patched downstream?

fwiw that's a nice side effect of #1603 for the local databases, though when @another-rex and I discussed it yesterday we weren't a fan of how it meant we would...

As with others above, I've started getting this infrequently with some work I'm doing with Docker - previously I've been using docker for just local development which was mainly `docker...

The security issue only impacts the v10 and v11 lines of `glob`, so no action should be needed by Jest to enable resolving the security vuln

Related to https://github.com/vercel/vercel/issues/11543

You should be able to use [`osv-scanner.toml` files for most of this](https://google.github.io/osv-scanner/configuration/) - if you create a config file with the following, the scanner will completely ignore the directory: ```toml...

I'm getting this quite a lot suddenly on https://github.com/google/osv-scanner - this only started happening in the last couple of weeks and afaik there have not been any changes to the...

@thomasrockhu-codecov I don't know as I'm not the owner of the repository, but I've not seen this failure for a few weeks so I assume it's just been fixed 🤷

fwiw our type-checking is breaking on v9.39 due to `@types/eslint-scope` which we have to require for `vue-eslint-parser`. A min reproduction should be: ``` // eslint.config.js const parserVueESLintParser = require('vue-eslint-parser'); /**...

> Using npm shrinkwrap, people still have the option of manually overriding dependencies if they really need to using the [overrides](https://docs.npmjs.com/cli/v8/configuring-npm/package-json#overrides) field. However, I don't think this will be necessary...