Different UUID in Project.toml and registry

I was tracking down a problem with my packages, and I think it stems from

having a different UUID than in

Is this supposed to happen? Did I make a mistake somewhere?

My guess is this is an artifact of the METADATA->JuliaRegistries pipeline we have now, and that when you first registered the package it ignored the UUID in your Project.toml file and generated a new one for you. Hopefully someone who knows more can confirm or correct this. (If it’s correct, I’d also guess it’s a bug worth reporting to Pkg.jl.)

2 Likes

Correct. Just update to the one in the registry and all should be well.

Is there any reason not to use the one in the Project.toml file, as long as it’s unique? Seems like this will come up a lot in the future.

1 Like

Will do, but this affects 4-5 packages I registered recently, with interdependencies, so it will be a bit cumbersome.

Is there an existing issue for this?

Opened an issue: