# Do AutoMerge of Julia Registry and CI use the same package compatibility rule?

**URL:** <https://discourse.julialang.org/t/do-automerge-of-julia-registry-and-ci-use-the-same-package-compatibility-rule/80238>\
**Category:** General Usage\
**Tags:** package\
**Created:** [April 29, 2022, 2:20am UTC](https://discourse.julialang.org/t/do-automerge-of-julia-registry-and-ci-use-the-same-package-compatibility-rule/80238 "2022-04-29T02:20:47Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![BVPs](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/bvps/32/2190_2.png) [@BVPs](https://discourse.julialang.org/u/BVPs)\
**Post date:** [April 29, 2022, 2:20am UTC](https://discourse.julialang.org/t/do-automerge-of-julia-registry-and-ci-use-the-same-package-compatibility-rule/80238/1 "2022-04-29T02:20:47Z")

</div>

I am very puzzled by the behavior of AutoMerge process of the Julia Registry.  
I had difficulty registering my updated version of the package [GitHub - UCD4IDS/MultiscaleGraphSignalTransforms.jl: MultiscaleGraphSignalTransforms.jl is a collection of software tools written in the Julia programming language for graph signal processing including HGLET, GHWT, eGHWT, NGWP, Lapped NGWP, and Lapped HGLET. Some of them were originally written in MATLAB by Jeff Irion, but we added more functionalities, e.g., eGHWT, NGWP, etc.](https://github.com/UCD4IDS/MultiscaleGraphSignalTransforms.jl)

I had to nail the version of `Clp` package in my repo’s Project.toml under compat as `Clp = "1.0.1"` for successful push and registry. If I just set up `Clp = "1"`, then for the CI tests, it tries to use `v1.0.1` as expected. However, AutoMerge (1, ubuntu-latest, x64) tries to use `Clp v1.0.0` and fails. I do not understand why AutoMerge and CI try to set up `Clp` of different versions.  
I really want to avoid this kind of problems in the future when I register updated packages.  
Thanks for your help!