If you have a package in your project / deps, it should have a bound. So that is what the PR is adding for you.
Understood, but these packages are part of Julia itself (aren’t they?), so the julia compat fixes them already. Aren’t the compats on those individual packages merely duplicative?
BTW the workaround works, and dependabot now happily ignores all subprojects.
see PSA: Compat requirements in the General registry are changing
That could be why setting Julia compat to 1.10 helps.
Thanks! Hadn’t seen or, more likely, had forgotten that.
So we made dependabot more correct by respecting the actual stdlib compat for the minimum declared julia version, but there was a bug where dependabot wasn’t inheriting the julia compat entry from the main project into the test/Project.toml (or any workspace sub-project), so dependabot thought there was no lower julia compat in those other projects.
That’s fixed now. But there are a bunch of other bugfixes queued up too.
Sorry for the noise!
Another good place to report dependabot issues is the #dependabot slack channel.
Sure, but I am using workspaces and my main Project.toml already specifies julia = 1.10, so it should be inherited by all sub-projects in the workspace. Anyhow, I guess this is or will be fixed soon.