Change JuliaSyntaxHighlighting UUID #56852
Conversation
Unfortunately during development of the backported version of this stdlib, to avoid potential sysimage issues the UUID was temporarilly changed and I forgot to change it back. This mistake lead to the backport/compat verison of the package having a different UUID from the in-tree stdlib. Beyond this being an embarassing mistake, it's also a pain because it means that we now have incorrect/invalid manifests. A small mercy is that 1.12 hasn't been released yet, so the discrepancy currently only affects people using development Julia versions. Changing the UUID here will require these people to regenerate their manifests, but this seems like the lesser of too evils.
| uuid = "dc6e5ff7-fb65-4e79-a425-ec3bc9c03011" | ||
| uuid = "ac6e5ff7-fb65-4e79-a425-ec3bc9c03011" |
There was a problem hiding this comment.
I'm a little confused, it seems that the UUID of JuliaSyntaxHighlighting.jl is specified as dc6e5ff7-fb65-4e79-a425-ec3bc9c03011 from the first commit.
So the current UUID seems to be correct?
There was a problem hiding this comment.
Yea, so the mistake at the heart of this is:
development of the backported version of this stdlib, to avoid potential sysimage issues the UUID was temporarilly changed and I forgot to change it back.
The changed UUID (ac6e...) is what was registered in General as the backport/compat version: https://github.com/JuliaRegistries/General/blob/master/J/JuliaSyntaxHighlighting/Package.toml#L2
There was a problem hiding this comment.
I think JuliaSyntaxHighlighting.jl also needs a pr to change the UUID and the two prs might want to be merged at the same time?
TLDR; I made a silly mistake a while back, and this seems like the least bad option.
Unfortunately during development of the backported version of this stdlib, to avoid potential sysimage issues the UUID was temporarilly changed and I forgot to change it back.
This mistake lead to the backport/compat verison of the package having a different UUID from the in-tree stdlib. Beyond this being an embarassing mistake, it's also a pain because it means that we now have incorrect/invalid manifests.
A small mercy is that 1.12 hasn't been released yet, so the discrepancy currently only affects people using development Julia versions. Changing the UUID here will require these people to regenerate their manifests, but this seems like the lesser of too evils.
Appologies for the hassle all.