Zoltán Lehóczky

What's the security reason?

The last couple of runs failed with various different errors, as visible in the output of the workflow run. One error that appeared thrice in slightly different variations, including [the...

GitHub support only pointed to the docs for now BTW, what I've previously read but didn't help.

Unfortunately, this isn't fixed. Dependabot has a limitation of 150 manifests per repo: https://docs.github.com/en/enterprise-cloud@latest/code-security/supply-chain-security/understanding-your-software-supply-chain/troubleshooting-the-dependency-graph#are-there-limits-which-affect-the-dependency-graph-data According to GitHub support, we have 190 (we have 217 projects in the solution but apparently,...

I think that's already the case. In Dependabot terminology, everything that may reference a package is a "manifest", I think. I.e. package.json for NPM, and csproj for NuGet. Since we...

Not yet fixed, see: https://github.com/OrchardCMS/OrchardCore/pull/16820#issuecomment-2392452285

https://github.com/OrchardCMS/OrchardCore/pull/16827 should be a good fix now.

Argh: https://github.com/OrchardCMS/OrchardCore/actions/runs/11178578942 `update_not_possible`, for `libphonenumber-csharp`, no details. But why? This should be a trivial update. I'm updating this manually once, and then we'll see if Dependabot will work, but I'm...

Still not working: https://github.com/OrchardCMS/OrchardCore/actions/runs/11203765523/job/31141396767 I'm out of ideas why. Waiting for the reply of GitHub support.

Sebastien started to work on a custom .NET CLI implementation instead of Dependabot here: https://github.com/OrchardCMS/OrchardCore/tree/sebros/outdated In case we can't use Dependabot, what appears the be the case currently (but I'm...