Repository navigation
Default manifests carry a stale project hash after the package rename #18
Description
The package rename (e990803) changed Project.toml without re-resolving the two tracked default manifests, so the project hash stored in each no longer matches. For Manifest-v1.13.toml.default the stored hash is 33a8fd38… and the current one is 507c1efd…. The package still installs and loads, but Pkg reports the manifest as out of date.
The fix is to run bin/update_default_manifests on a machine whose Julia matches the one that wrote the manifests (1.13.2 for the 1.13 file). It should change only the hash. The agents box has Julia 1.13.0, and a resolve there downgrades seven bundled stdlib JLLs, so it was left out of #16.
Activity
ufechner7 commentedon Oct 23, 2026
Fixed in ad19143: re-resolved both default manifests with
bin/update_default_manifests --resolve(Julia 1.13.2 and 1.12.7). The rename mismatch itself was already gone by ad0427f, but a94171b (DataFrames added toexamples/Project.toml) made both stale again. Checked on a clean checkout: the storedproject_hashnow matches the computed one for 1.13 and 1.12.