# PSA: Add Downgrade CI to Better Check Version Compatibility

**URL:** <https://discourse.julialang.org/t/psa-add-downgrade-ci-to-better-check-version-compatibility/110063>\
**Category:** Community\
**Tags:** package, package-manager, semver, versioning\
**Created:** [February 11, 2024, 12:56pm UTC](https://discourse.julialang.org/t/psa-add-downgrade-ci-to-better-check-version-compatibility/110063 "2024-02-11T12:56:01Z")\
**Posts on this page:** 1\
**Showing post:** 15

<div class="post-metadata">

**Author:** ![lrnv](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/lrnv/32/19373_2.png) [@lrnv](https://discourse.julialang.org/u/lrnv)\
**Post date:** [February 13, 2024, 2:57pm UTC](https://discourse.julialang.org/t/psa-add-downgrade-ci-to-better-check-version-compatibility/110063/15 "2024-02-13T14:57:34Z")

</div>

> [@CameronBieganek](#):
>
> I don’t think this is your responsibility. Your compatibility bounds are perfectly reasonable. It is the job of the package manager to resolve a compatible set of dependencies. If the downgrade CI pins every package at the minimum version, but it’s not actually an installable environment, then that’s a problem with the downgrade CI.

Yes, this is the problem I am currently having. Pinning all my dependencies to their lower bounds ends up in a contradictory environment, but each of these bounds are actually achievable taken separately so I do not want to change them. The issue is that now I cannot get a “all-lower-bound” environement to test my functionalities in…

Maybe the compat pinning action could do something here and try to “resolve as low as possible” the environment instead of “resolving as high as possible” like Pkg is doing normally.

---

_[View the full topic](https://discourse.julialang.org/t/psa-add-downgrade-ci-to-better-check-version-compatibility/110063)._