# Package compatibility caps

**URL:** <https://discourse.julialang.org/t/package-compatibility-caps/15301>\
**Category:** Announcements\
**Tags:** announcement, packages, package-manager\
**Created:** [September 21, 2018, 6:24pm UTC](https://discourse.julialang.org/t/package-compatibility-caps/15301 "2018-09-21T18:24:06Z")\
**Posts on this page:** 17\
**Page:** 3

<div class="post-metadata">

**Author:** ![stevengj](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/stevengj/32/71_2.png) [@stevengj](https://discourse.julialang.org/u/stevengj)\
**Post date:** [September 23, 2018, 8:35pm UTC](https://discourse.julialang.org/t/package-compatibility-caps/15301/41 "2018-09-23T20:35:20Z")

</div>

> [@MartinOtter](#):
>
> Please **uncap** the last version of [ModiaMath](https://github.com/ModiaSim/ModiaMath.jl)

Why would this be capped? It was tagged after July 14.

---

<div class="post-metadata">

**Author:** ![Shpiel\_Meister](https://avatars.discourse-cdn.com/v4/letter/s/77aa72/32.png) [@Shpiel\_Meister](https://discourse.julialang.org/u/Shpiel_Meister)\
**Post date:** [September 23, 2018, 9:12pm UTC](https://discourse.julialang.org/t/package-compatibility-caps/15301/42 "2018-09-23T21:12:17Z")

</div>

like the strategy. i’t’s pragmatic, just like Julia

thx

---

<div class="post-metadata">

**Author:** ![StefanKarpinski](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/stefankarpinski/32/24_2.png) [@StefanKarpinski](https://discourse.julialang.org/u/StefanKarpinski)\
**Post date:** [September 23, 2018, 9:12pm UTC](https://discourse.julialang.org/t/package-compatibility-caps/15301/43 "2018-09-23T21:12:54Z")

</div>

I just checked and it is, in fact, not capped so there’s nothing to be done here.

---

<div class="post-metadata">

**Author:** ![cstjean](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/cstjean/32/1444_2.png) [@cstjean](https://discourse.julialang.org/u/cstjean)\
**Post date:** [September 23, 2018, 9:42pm UTC](https://discourse.julialang.org/t/package-compatibility-caps/15301/44 "2018-09-23T21:42:09Z")

</div>

Sorry if I’ve missed a link in this thread, but is there a list somewhere of which package was affected? I looked for a METADATA PR and couldn’t find it.

---

<div class="post-metadata">

**Author:** ![StefanKarpinski](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/stefankarpinski/32/24_2.png) [@StefanKarpinski](https://discourse.julialang.org/u/StefanKarpinski)\
**Post date:** [September 24, 2018, 1:38am UTC](https://discourse.julialang.org/t/package-compatibility-caps/15301/45 "2018-09-24T01:38:23Z")

</div>

[https://github.com/JuliaRegistries/General/commit/0c75a4d9bd1f8d8386216a008792cbf6d105345e](https://github.com/JuliaRegistries/General/commit/0c75a4d9bd1f8d8386216a008792cbf6d105345e)

---

<div class="post-metadata">

**Author:** ![heliosdrm](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/heliosdrm/32/3851_2.png) [@heliosdrm](https://discourse.julialang.org/u/heliosdrm)\
**Post date:** [September 24, 2018, 7:05pm UTC](https://discourse.julialang.org/t/package-compatibility-caps/15301/46 "2018-09-24T19:05:26Z")

</div>

Hi, what about the opposite case? I.e. I look at my packages and discover that an old version not meant to support Julia 1.0 (if fact has deprecation warnings for 0.7, so it would break in 1.0) is _not_ capped. Must I report it or make some PR?

---

<div class="post-metadata">

**Author:** ![kristoffer.carlsson](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/kristoffer.carlsson/32/22_2.png) [@kristoffer.carlsson](https://discourse.julialang.org/u/kristoffer.carlsson)\
**Post date:** [September 24, 2018, 7:30pm UTC](https://discourse.julialang.org/t/package-compatibility-caps/15301/47 "2018-09-24T19:30:48Z")

</div>

You can make a PR that adds upper bounds to the REQUIRE files that doesn’t support 0.7 / 1.0.

---

<div class="post-metadata">

**Author:** ![jarvist](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/jarvist/32/123_2.png) [@jarvist](https://discourse.julialang.org/u/jarvist)\
**Post date:** [October 10, 2018, 9:14pm UTC](https://discourse.julialang.org/t/package-compatibility-caps/15301/48 "2018-10-10T21:14:39Z")

</div>

So what’s the best way to understand whether your package has such a cap on it?

Finding my way to: [General/Compat.toml at master · JuliaRegistries/General · GitHub](https://github.com/JuliaRegistries/General/blob/master/P/PolaronMobility/Compat.toml)  
indicates that this little package does.

And what’s the recommended way to fix this?  
Push another minor version with the `julia 0.6 2-` REQUIRE trick of Stefan, and let Attobot sort it out? Or construct a hand-written pull-request to METADATA?

---

<div class="post-metadata">

**Author:** ![StefanKarpinski](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/stefankarpinski/32/24_2.png) [@StefanKarpinski](https://discourse.julialang.org/u/StefanKarpinski)\
**Post date:** [October 10, 2018, 11:26pm UTC](https://discourse.julialang.org/t/package-compatibility-caps/15301/49 "2018-10-10T23:26:10Z")

</div>

Does it work on 1.0?

---

<div class="post-metadata">

**Author:** ![jarvist](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/jarvist/32/123_2.png) [@jarvist](https://discourse.julialang.org/u/jarvist)\
**Post date:** [October 11, 2018, 8:30am UTC](https://discourse.julialang.org/t/package-compatibility-caps/15301/50 "2018-10-11T08:30:28Z")

</div>

Yep, tests AOK. I didn’t have to do much to get it working on 1.0 - just a few places with scope + waiting for Optim to become available.

> **[Travis CI - Test and Deploy with Confidence](https://app.travis-ci.com/jarvist/PolaronMobility.jl)**
>
> Travis CI enables your team to test and ship your apps with confidence. Easily sync your projects with Travis CI and you'll be testing your code in minutes.

---

<div class="post-metadata">

**Author:** ![StefanKarpinski](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/stefankarpinski/32/24_2.png) [@StefanKarpinski](https://discourse.julialang.org/u/StefanKarpinski)\
**Post date:** [October 11, 2018, 3:03pm UTC](https://discourse.julialang.org/t/package-compatibility-caps/15301/51 "2018-10-11T15:03:27Z")

</div>

Not much is still something. If you make a new release that claims to be 1.0 compatible that will be taken at face value.

---

<div class="post-metadata">

**Author:** ![jarvist](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/jarvist/32/123_2.png) [@jarvist](https://discourse.julialang.org/u/jarvist)\
**Post date:** [October 11, 2018, 3:13pm UTC](https://discourse.julialang.org/t/package-compatibility-caps/15301/52 "2018-10-11T15:13:54Z")

</div>

As in, change my REQUIRE line to  
`julia 0.6 0.7 1.0 `  
?  
Or your `julia 0.6 2-` method?

---

<div class="post-metadata">

**Author:** ![StefanKarpinski](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/stefankarpinski/32/24_2.png) [@StefanKarpinski](https://discourse.julialang.org/u/StefanKarpinski)\
**Post date:** [October 11, 2018, 4:26pm UTC](https://discourse.julialang.org/t/package-compatibility-caps/15301/53 "2018-10-11T16:26:36Z")

</div>

As in just make a new release that actually works on 1.0 and leave the REQUIRE file alone. The `julia 0.6 2-` change is _only_ required for versions of packages that were tagged before July 14th. You only have to change the require file in METADATA.jl if there’s an old version that works on 1.0 correctly and was erroneously capped. It sounds like that is not the case here since you had to make changes to get it working on 1.0. So just make a new release with `julia 0.6` or `julia 0.7` depending on what it actually supports.

---

<div class="post-metadata">

**Author:** ![jarvist](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/jarvist/32/123_2.png) [@jarvist](https://discourse.julialang.org/u/jarvist)\
**Post date:** [October 11, 2018, 4:37pm UTC](https://discourse.julialang.org/t/package-compatibility-caps/15301/54 "2018-10-11T16:37:52Z")

</div>

Stefan, I did try to do this. I’ll try a semantic-versioning minor-number increment and see if that helps.

---

<div class="post-metadata">

**Author:** ![StefanKarpinski](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/stefankarpinski/32/24_2.png) [@StefanKarpinski](https://discourse.julialang.org/u/StefanKarpinski)\
**Post date:** [October 11, 2018, 4:51pm UTC](https://discourse.julialang.org/t/package-compatibility-caps/15301/55 "2018-10-11T16:51:39Z")

</div>

Something seems to be wrong with the process that generates the new registry from METADATA here, I’ll investigate. Sorry for the trouble and for not understanding what your trouble was before.

---

<div class="post-metadata">

**Author:** ![StefanKarpinski](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/stefankarpinski/32/24_2.png) [@StefanKarpinski](https://discourse.julialang.org/u/StefanKarpinski)\
**Post date:** [October 11, 2018, 5:15pm UTC](https://discourse.julialang.org/t/package-compatibility-caps/15301/56 "2018-10-11T17:15:01Z")

</div>

I was misremembering / misstating the heuristic before. I’ve added a rule that if someone registers a new version (since yesterday) that claims to support 0.7 or 1.0 then we just take that claim at face value.

---

<div class="post-metadata">

**Author:** ![jarvist](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/jarvist/32/123_2.png) [@jarvist](https://discourse.julialang.org/u/jarvist)\
**Post date:** [October 12, 2018, 10:50am UTC](https://discourse.julialang.org/t/package-compatibility-caps/15301/57 "2018-10-12T10:50:14Z")

</div>

Great! Many thanks Stefan. Happily installs + tests on 1.0.1 now.

[Previous page](https://discourse.julialang.org/t/package-compatibility-caps/15301.md?page=2)