How to find out why packages are downgraded


I’ve just run


and found some large downgrades to packages I care about, for example:

  [70588ee8] ↓ CSSUtil v0.1.1 ⇒ v0.1.0
  [336ed68f] ↓ CSV v0.7.7 ⇒ v0.6.1
  [5d742f6a] ↓ CSVFiles v1.0.0 ⇒ v0.16.1
  [324d7699] ↓ CategoricalArrays v0.8.2 ⇒ v0.7.7
    [5ae59095] ↓ Colors v0.12.4 ⇒ v0.11.2
  [34da2185] ↓ Compat v3.15.0 ⇒ v2.2.1
   [7ad07ef1] ↓ CoupledFields v0.2.0 ⇒ v0.1.0
  [5721bf48] ↓ DataVoyager v1.0.0 ⇒ v0.3.1

is there a simple way of finding out which dependencies have caused this?



1 Like

You could try upgrading any of these to a specific latest version (pkg> add SomePackage@ver), then the resolver will give you more details. But it could also be a bug like

Also more generally it is a good idea to create separate environments for specific scripts/tasks to minimise the scope for incompatibilities that lead to downgrades.

I don’t know your specific situation of course and whether you might actually just need all those packages at the same time, but it looks like you have a lot of packages installed in the same environment, so to the extent that you don’t actually use them concurrently for one piece of work, it makes sense to split environments.

1 Like