# Github Dependency Graphs

**URL:** <https://discourse.julialang.org/t/github-dependency-graphs/40081>\
**Category:** Tooling\
**Created:** [May 24, 2020, 4:48pm UTC](https://discourse.julialang.org/t/github-dependency-graphs/40081 "2020-05-24T16:48:27Z")\
**Posts on this page:** 1\
**Showing post:** 5

<div class="post-metadata">

**Author:** ![tbeason](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/tbeason/32/15898_2.png) [@tbeason](https://discourse.julialang.org/u/tbeason)\
**Post date:** [May 24, 2020, 6:11pm UTC](https://discourse.julialang.org/t/github-dependency-graphs/40081/5 "2020-05-24T18:11:48Z")

</div>

> [@Managing dependencies in packages](https://discourse.julialang.org/t/managing-dependencies-in-packages/34474):
>
> How do I account for package dependencies that vary depending on the Julia version when running CI via travis? My situation: The SpecialFunctions package in its latest version 0.10.0 requires Julia 1.3 or above. When writing a new package that should be supported for Julia 1.0 and above, does that mean I have to resort to the version of SpecialFunctions that supports Julia 1.0 (which is 0.7.2, I believe)? Or is there a way in the Project.toml and Manifest.toml files to support something like i…

---

_[View the full topic](https://discourse.julialang.org/t/github-dependency-graphs/40081)._