Package marked with ^ but new version is not available

[LilithHafner]

I released BasicAutoloads 1.0.3 45 hours ago and then also 1.0.4. Pkg indicates that an update is available, but when I try to update, nothing happens.

x@x:~$ julia
  o  | Version 1.11.2 (2024-12-01)
 o o | Official https://julialang.org/ release
(@v1.11) pkg> st
Status `~/.julia/environments/v1.11/Project.toml`
⌃ [09cdc199] BasicAutoloads v1.0.2
  [6e4b80f9] BenchmarkTools v1.5.0
  [336ed68f] CSV v0.10.15
  [0ca39b1e] Chairmarks v1.3.1
  [a93c6f00] DataFrames v1.7.0
  [6fe1bfb0] OffsetArrays v1.14.1
  [295af30f] Revise v3.6.4
  [2913bbd2] StatsBase v0.34.3
Info Packages marked with ⌃ have new versions available and may be upgradable.

(@v1.11) pkg> up
    Updating registry at `~/.julia/registries/General.toml`
  No Changes to `~/.julia/environments/v1.11/Project.toml`
  No Changes to `~/.julia/environments/v1.11/Manifest.toml`

(@v1.11) pkg> st
Status `~/.julia/environments/v1.11/Project.toml`
  [09cdc199] BasicAutoloads v1.0.2
  [6e4b80f9] BenchmarkTools v1.5.0
  [336ed68f] CSV v0.10.15
  [0ca39b1e] Chairmarks v1.3.1
  [a93c6f00] DataFrames v1.7.0
  [6fe1bfb0] OffsetArrays v1.14.1
  [295af30f] Revise v3.6.4
  [2913bbd2] StatsBase v0.34.3

(@v1.11) pkg> add [email protected]
   Resolving package versions...
ERROR: Unsatisfiable requirements detected for package BasicAutoloads [09cdc199]:
 BasicAutoloads [09cdc199] log:
 ├─possible versions are: 1.0.0 - 1.0.2 or uninstalled
 ├─restricted to versions * by project [022bee91], leaving only versions: 1.0.0 - 1.0.2
 │ └─project [022bee91] log:
 │   ├─possible versions are: 0.0.0 or uninstalled
 │   └─project [022bee91] is fixed to version 0.0.0
 └─restricted to versions 1.0.4 by an explicit requirement — no versions left

See also JuliaRegistries/General#120562

[IanButterworth]

Odd. I don't see the new versions, nor the upgradable indicator.

(@v1.11) pkg> add BasicAutoloads
    Updating registry at `~/.julia/registries/General.toml`
   Resolving package versions...
   Installed BasicAutoloads ─ v1.0.2
    Updating `~/.julia/environments/v1.11/Project.toml`
  [09cdc199] + BasicAutoloads v1.0.2
    Updating `~/.julia/environments/v1.11/Manifest.toml`
  [09cdc199] + BasicAutoloads v1.0.2
Precompiling project...
  2 dependencies successfully precompiled in 2 seconds. 114 already precompiled.

(@v1.11) pkg> st
Status `~/.julia/environments/v1.11/Project.toml`
  [1520ce14] AbstractTrees v0.4.5
  [09cdc199] BasicAutoloads v1.0.2
  [aa65fe97] SnoopCompile v3.0.1
  [e2b509da] SnoopCompileCore v3.0.0

and my registry is newer than your releases, I believe.

% curl -sLI https://pkg.julialang.org/registries.conservative
HTTP/2 301
server: Varnish
retry-after: 0
location: https://us-east.pkg.julialang.org/registries.conservative
x-geo-continent: NA
x-geo-country: US
x-geo-region: MA
accept-ranges: bytes
date: Thu, 05 Dec 2024 13:22:32 GMT
via: 1.1 varnish
x-served-by: cache-bos4636-BOS
x-cache: HIT
x-cache-hits: 0
x-timer: S1733404953.830180,VS0,VE0
content-length: 0

HTTP/2 200
server: nginx/1.26.0
date: Thu, 05 Dec 2024 13:22:32 GMT
content-type: application/octet-stream
content-length: 88
last-modified: Thu, 05 Dec 2024 06:42:30 GMT
etag: "67514b56-58"
accept-ranges: bytes
x-lb-strategy: pkgservers_roundrobin

[IanButterworth]

But I noticed that it only showed in your first status call. So perhaps your manifest was in some odd state and the up re-resolved and fixed it.

[LilithHafner]

Ah, yes. I expect this is due to my manifest reflecting the existence of a version 1.0.4 due to previously using an eager registry and then re-resolving switched to the out of date registry. In which case this is a duplicate of JuliaRegistries/General#120731

[IanButterworth]

Oh so it's not the manifest state. It was that you had a local registry that said newer versions were available, but doing up updated the eager registry to an older conservative one.