# Backpropagate compat bounds

**URL:** https://discourse.julialang.org/t/backpropagate-compat-bounds/30737
**Category:** General Usage
**Tags:** development
**Created:** [November 5, 2019, 9:56am UTC](https://discourse.julialang.org/t/backpropagate-compat-bounds/30737 "2019-11-05T09:56:08Z")
**Posts on this page:** 1
**Showing post:** 3

<div class="post-metadata">

### Author: ![fredrikekre](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/fredrikekre/32/1688_2.png) [@fredrikekre](https://discourse.julialang.org/u/fredrikekre)
#### Post date: [November 5, 2019, 10:28am UTC](https://discourse.julialang.org/t/backpropagate-compat-bounds/30737/3 "2019-11-05T10:28:34Z")

</div>

I tried to explain in [this comment](https://discourse.julialang.org/t/please-be-mindful-of-version-bounds-and-semantic-versioning-when-tagging-your-packages/30708/29) why I am a bit hesitant to modify the registry.

Basically, relaxing bounds should be safe, but can have non-local effects that you can no predict, and that might also be damaging. Tightening bounds can result in users ending up in an “impossible” state (according to the new registry), which the package manager does not like.

---

_[View the full topic](https://discourse.julialang.org/t/backpropagate-compat-bounds/30737)._