# Breaking the shackles -- A new registry, free of any bounds

**URL:** <https://discourse.julialang.org/t/breaking-the-shackles-a-new-registry-free-of-any-bounds/30749>\
**Category:** Community\
**Created:** [November 5, 2019, 2:56pm UTC](https://discourse.julialang.org/t/breaking-the-shackles-a-new-registry-free-of-any-bounds/30749 "2019-11-05T14:56:17Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![Tamas\_Papp](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/tamas_papp/32/25949_2.png) [@Tamas\_Papp](https://discourse.julialang.org/u/Tamas_Papp)\
**Post date:** [November 9, 2019, 3:33pm UTC](https://discourse.julialang.org/t/breaking-the-shackles-a-new-registry-free-of-any-bounds/30749/3 "2019-11-09T15:33:15Z")

</div>

I think this registry is just a tongue-in-cheek demonstration of a point made in this topic:

> [@Please be mindful of version bounds and semantic versioning when tagging your packages](https://discourse.julialang.org/t/please-be-mindful-of-version-bounds-and-semantic-versioning-when-tagging-your-packages/30708/):
>
> In order for packages to be automatically merged into the general registry, it is required that the package’s Project.toml contains a compat section giving upper version bounds on all direct dependencies. I wanted to bring a few concerns to the forefront of the minds of package developers, so that we don’t inadvertently get burned by this practice: Don’t tag your new version as containing breaking changes unless it really does For versions ≥ v"1.0", any time there are version differences of a…

and is not intended to be used for anything serious.

---

_[View the full topic](https://discourse.julialang.org/t/breaking-the-shackles-a-new-registry-free-of-any-bounds/30749)._