Diagnostics for Pkg.update() non-latest version

question
#1

When Pkg.update() does not upgrade to the latest version of a package, is it possible to learn why? Eg something along the lines of “because I calculated the dependencies and can’t figure out a way to do it” or “a package was pinned”.

Lost in transition: the current state of the Julia ecosystem?
#2

It would also be great if Pkg.status() would show which packages are not at the most recent tag:

julia> Pkg.status()
...
 - SmoothingSplines              0.1.2              master                                                                                            
 - SortingAlgorithms             0.1.1              held back by SomePackage; most recent v0.2.1                                                                                                
...
#3

Good point, please consider opening an issue about this.

#4

I found an existing one:

https://github.com/JuliaLang/julia/issues/17571