# JuliaCIBot on Modia fails for Julia 1.0, but Travis is successful

**URL:** <https://discourse.julialang.org/t/juliacibot-on-modia-fails-for-julia-1-0-but-travis-is-successful/15993>\
**Category:** General Usage\
**Created:** [October 7, 2018, 12:58pm UTC](https://discourse.julialang.org/t/juliacibot-on-modia-fails-for-julia-1-0-but-travis-is-successful/15993 "2018-10-07T12:58:16Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![tkoolen](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/tkoolen/32/1603_2.png) [@tkoolen](https://discourse.julialang.org/u/tkoolen)\
**Post date:** [October 7, 2018, 1:36pm UTC](https://discourse.julialang.org/t/juliacibot-on-modia-fails-for-julia-1-0-but-travis-is-successful/15993/3 "2018-10-07T13:36:53Z")

</div>

I see that Modia.jl has a `Manifest.toml` checked in. Not 100% sure, but I believe that the current practice for working with METADATA.jl is to not do this. You need a `REQUIRE` file and you can have a `Project.toml` file, but not a `Manifest.toml`, I think. At least I don’t do it for my packages. I’m not sure where/whether this is documented; I was at least expecting this information in the `README.md` for METADATA.jl, but it appears it hasn’t been updated for 0.7/1.0.

---

_[View the full topic](https://discourse.julialang.org/t/juliacibot-on-modia-fails-for-julia-1-0-but-travis-is-successful/15993)._