Let me know what sort of bugs or weird behaviour you've seen, and I'll make sure we look into it.

So while I'm a huge fan of dependabot; something that is supposed to reduce toil actually creates quite a lot of maintenance work for me.

I know this is likely a different team, but github.com/dependabot/dependabot-core/issues/9916 unignore just does nothing.

Yeah, not directly related to our work, but I can try and get eyes on it.

I don't have an issue number for this, but there are several cases where certain packages are just never updated and have to be done manually. This is not specific to the .NET engine, I see the same issue with GitHub actions.

If you can share a repo and a package you expect to get updates, I can create an issue and triage it.

I can only find examples of this on private repositories on fine, but I have a project that should be seeing updates for: - 2 x private packages that I have hosted on AWS - Amazon.Lambda.AspNetCoreServer.Hosting - AwesomeAssertions - FastEndpoints - Microsoft.AspNetCore.Mvc.Testing /1

- Microsoft.Extensions.Configuration - Microsoft.Extensions.DependencyInjection.Abstractions - Microsoft.Extensions.Logging - Microsoft.Extensions.Options.ConfigurationExtensions - Xunit.OpenCategories - xunit.runner.visualstudio /2

Thanks @jamiemagee.bsky.social github.com/dependabot/d... this one appeared to be fixed but there seems to be a slight regression on it where groups in the dependabot.yml are ignored.

I'm not sure I see much about groups in that one. Is it related to this? github.com/dependabot/d...

another github.com/baynezy/FoxP...

But if you need another example for that ticket here you go: github.com/baynezy/Html... those have just been randomly dumped together

Thanks, I added it to the issue.

So I have this issue too, but I also have issues where I have defined a group, but dependabot insists on creating a single PR per dependency.