# PSA: GitHub Dependabot now supports Julia
**URL:** https://discourse.julialang.org/t/psa-github-dependabot-now-supports-julia/134997
**Category:** Tooling
**Tags:** announcement
**Created:** [January 12, 2026, 5:38am UTC](https://discourse.julialang.org/t/psa-github-dependabot-now-supports-julia/134997 "2026-01-12T05:38:33Z")
**Posts on this page:** 7
**Page:** 2
### Author:  [@kellertuer](https://discourse.julialang.org/u/kellertuer)
#### Post date: [September 24, 2026, 7:58am UTC](https://discourse.julialang.org/t/psa-github-dependabot-now-supports-julia/134997/21 "2026-09-24T07:58:51Z")
If you have a package in your project / deps, it should have a bound. So that is what the PR is adding for you.
---
### Author:  [@TimG](https://discourse.julialang.org/u/TimG)
#### Post date: [September 24, 2026, 8:04am UTC](https://discourse.julialang.org/t/psa-github-dependabot-now-supports-julia/134997/22 "2026-09-24T08:04:36Z")
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?
---
### Author:  [@Eben60](https://discourse.julialang.org/u/Eben60)
#### Post date: [September 24, 2026, 8:30am UTC](https://discourse.julialang.org/t/psa-github-dependabot-now-supports-julia/134997/23 "2026-09-24T08:30:15Z")
> [@ranocha](#):
>
> We got these for something like `test/Project.toml` and `docs/Project.toml` as well
> [@Eben60](#):
>
> we found a possible solution - or rather a workaround - which is being tried right now.
BTW the workaround works, and dependabot now happily ignores all subprojects.
---
### Author:  [@Eben60](https://discourse.julialang.org/u/Eben60)
#### Post date: [September 24, 2026, 8:34am UTC](https://discourse.julialang.org/t/psa-github-dependabot-now-supports-julia/134997/24 "2026-09-24T08:34:14Z")
> [@Tamas\_Papp](#):
>
> nonsensical compat bounds for standard libraries
see [PSA: Compat requirements in the General registry are changing](https://discourse.julialang.org/t/psa-compat-requirements-in-the-general-registry-are-changing/104958)
> [@PSA: Compat requirements in the General registry are changing](https://discourse.julialang.org/t/psa-compat-requirements-in-the-general-registry-are-changing/104958/1):
>
> **If your package supports Julia 1.3 or earlier** , then for most stdlibs you should set:
>
> ```julia-auto
> [compat]
> StdlibName = "<0.0.1, 1"
>
> ```
That could be why setting Julia compat to 1.10 helps.
---
### Author:  [@TimG](https://discourse.julialang.org/u/TimG)
#### Post date: [September 24, 2026, 10:17am UTC](https://discourse.julialang.org/t/psa-github-dependabot-now-supports-julia/134997/25 "2026-09-24T10:17:41Z")
> [@Eben60](#):
>
> see [PSA: Compat requirements in the General registry are changing](https://discourse.julialang.org/t/psa-compat-requirements-in-the-general-registry-are-changing/104958)
Thanks! Hadn’t seen or, more likely, had forgotten that.
---
### Author:  [@ianshmean](https://discourse.julialang.org/u/ianshmean)
#### Post date: [September 24, 2026, 1:23pm UTC](https://discourse.julialang.org/t/psa-github-dependabot-now-supports-julia/134997/26 "2026-09-24T13:23:12Z")
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.
---
### Author:  [@Tamas\_Papp](https://discourse.julialang.org/u/Tamas_Papp)
#### Post date: [September 25, 2026, 9:20am UTC](https://discourse.julialang.org/t/psa-github-dependabot-now-supports-julia/134997/27 "2026-09-25T09:20:49Z")
> [@Eben60](#):
>
> see [PSA: Compat requirements in the General registry are changing](https://discourse.julialang.org/t/psa-compat-requirements-in-the-general-registry-are-changing/104958)
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.
[Previous page](https://discourse.julialang.org/t/psa-github-dependabot-now-supports-julia/134997.md?page=1)