# Versioning in a new Julia package

**URL:** <https://discourse.julialang.org/t/versioning-in-a-new-julia-package/74119>\
**Category:** New to Julia\
**Tags:** package\
**Created:** [January 6, 2022, 5:08am UTC](https://discourse.julialang.org/t/versioning-in-a-new-julia-package/74119 "2022-01-06T05:08:23Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Sushant-Padha](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/sushant-padha/32/32367_2.png) [@Sushant-Padha](https://discourse.julialang.org/u/Sushant-Padha)\
**Post date:** [January 6, 2022, 5:08am UTC](https://discourse.julialang.org/t/versioning-in-a-new-julia-package/74119/1 "2022-01-06T05:08:23Z")

</div>

I have created a Julia package, that I am trying to register at the General registry.

However, the pull request tests failed (twice now). This is the concerned [AutoMerge test](https://github.com/JuliaRegistries/General/runs/4723450160?check_suite_focus=true).

The error output is

```julia
ERROR: Unsatisfiable requirements detected for package TimetableSolver [df459030]:
 TimetableSolver [df459030] log:
 ├─possible versions are: 0.1.0 or uninstalled
 ├─restricted to versions 0.1.0 by an explicit requirement, leaving only versions 0.1.0
 └─restricted by julia compatibility requirements to versions: uninstalled — no versions left

```

And then, `import <PackageName>` also failed but I believe it may ultimately be because of this error.

This is my package on github: [TimetableSolver.jl](https://github.com/Sushant-Padha/TimetableSolver.jl). In the `Project.toml` and using `git tag` I have listed version `v0.1.0` for the package, and fixed all dependencies and compat to upper bounded.

My package is limited to `julia = "~1.6" # [1.6.0, 1.7.0)`, because the last time I tested with 1.7 (latest) my code failed. Do I need to update `Project.toml` to work with 1.7 and test my code accordingly?

---

<div class="post-metadata">

**Author:** ![Sushant-Padha](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/sushant-padha/32/32367_2.png) [@Sushant-Padha](https://discourse.julialang.org/u/Sushant-Padha)\
**Post date:** [January 6, 2022, 6:10am UTC](https://discourse.julialang.org/t/versioning-in-a-new-julia-package/74119/2 "2022-01-06T06:10:18Z")

</div>

I found the solution.

For me, as soon as I updated my julia version from `julia = "1.2 - 1.6"` to `julia = "~1.6"` the checks succeeded and my package was added to the registry. Wasn’t really a change more of a bugfix.

For anyone else, who stumbles on this post with a similar question, remember to use appropriate versioning for dependencies (including julia) and your own package. See [Compatibility](https://pkgdocs.julialang.org/v1/compatibility/) for more info on how to do this properly.

---

<div class="post-metadata">

**Author:** ![GunnarFarneback](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/gunnarfarneback/32/1827_2.png) [@GunnarFarneback](https://discourse.julialang.org/u/GunnarFarneback)\
**Post date:** [January 6, 2022, 9:58am UTC](https://discourse.julialang.org/t/versioning-in-a-new-julia-package/74119/3 "2022-01-06T09:58:54Z")

</div>

> [@Sushant-Padha](#):
>
> My package is limited to `julia = "^1.6" # [1.6.0, 1.7.0)`

Well, that’s not what `^1.6` means. [PackageCompatUI](https://github.com/GunnarFarneback/PackageCompatUI.jl) can be a useful tool to manage your compat settings and see what they effectively mean.

---

<div class="post-metadata">

**Author:** ![Sushant-Padha](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/sushant-padha/32/32367_2.png) [@Sushant-Padha](https://discourse.julialang.org/u/Sushant-Padha)\
**Post date:** [January 6, 2022, 3:26pm UTC](https://discourse.julialang.org/t/versioning-in-a-new-julia-package/74119/4 "2022-01-06T15:26:06Z")

</div>

Oh, thanks. I realized I was using the wrong symbol, should fix that.  
Thanks for the package link, it’s really useful.