# Package Registration Issues

**URL:** <https://discourse.julialang.org/t/package-registration-issues/104424>\
**Category:** Package Management\
**Tags:** general-registry\
**Created:** [September 30, 2023, 9:03am UTC](https://discourse.julialang.org/t/package-registration-issues/104424 "2023-09-30T09:03:12Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![goerz](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/goerz/32/3269_2.png) [@goerz](https://discourse.julialang.org/u/goerz)\
**Post date:** [September 30, 2023, 4:08pm UTC](https://discourse.julialang.org/t/package-registration-issues/104424/3 "2023-09-30T16:08:09Z")

</div>

> [@goerz](#):
>
> But, do you have a CI step that tests that your package actually runs with the very first 0.1 release of all of your dependencies, as well as all the latest releases?

Just to clarify: most people (myself included) don’t actually do this. See [Project.toml [compat] best practice: should I manually remove incompatible old dependency versions?](https://discourse.julialang.org/t/project-toml-compat-best-practice-should-i-manually-remove-incompatible-old-dependency-versions/103530)

In your case, I was just suggesting that your stated compatibilities are unusually broad, so you should actually verify them (at least manually, if not by CI).

What most people do, and what is probably the right solution for you as well: When you’re registering your new package, set the compat entry for all of your dependencies to the `x.y` that is the most recent release for that dependency. This means that your package will require that dependency version as a minimum, and also accept any future releases of the dependency that are not breaking according to semantic versioning (so all `0.y.*` versions and all `x.*.*` version for `x > 0`).

When you make new releases of your packages in the future, verify that the `compat` entry for all your dependencies is still ok (that is, your package still works with the given _minimum_ version). If not, update the compat entries to the most current release of your dependency.

---

_[View the full topic](https://discourse.julialang.org/t/package-registration-issues/104424)._