I registered a new version of a package , and the pull request was merged but when I install the package via ``Pkg.add```, the old version is installed. Why is this so and how can I fix it?

There might be some compatibility conflict holding it back. What happens if you do add CategoricalTimeSeries@1.1?

Oh you are right! There is a restriction on a [compat] concerning another package of mine called MotifRecognition. What puzzles me is that this package is no longer required in the latest version of CategoricalTimeSeries.jl, and is consequently not mentionned in the project.toml file. How can it be …

That’s not the issue—the new version is in the registry. It also installs v1.1.0 in a fresh environment. There’s some conflict with some other package that’s in the environment.

I just noticed that in a clean environment, the package installs correctly. Thank you for your help! I thought I had deleted all problematic packages in my main environment but apparently I didn’t.

I wish the resolver output was actually intelligible but I can never understand what it’s telling me.

Registered new release still pointing to old version

General Usage

GunnarFarneback October 8, 2021, 9:41pm 4

Do you have the new version in your copy of the General registry? Cf. General registry delays, and a workaround

Topic		Replies	Views
I am having a versioning problem General Usage	10	354	April 1, 2022
Package updated but not available (12 hours latter) General Usage package	13	1440	May 24, 2021
Deprecate old Registered Packages Versions and default to the Newest Version? General Usage package	18	1077	April 3, 2019
Pkg behaving differently for Package from Registry vs the direct URL General Usage package , pkg , dependencies , general-registry	2	148	June 6, 2024
Time traveling the dependencies of an older package version Package Management	13	347	December 20, 2024

Registered new release still pointing to old version

Related topics