You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Nothing good will come if the registered version number does not match the version number in Project.toml in the given treehash. That these are consistent should be verified and should be easy to do as part of the "code can be loaded" check.
The text was updated successfully, but these errors were encountered:
True, though we only run automerge on registrator PRs currently and registrator gets its version from the source’s Project.toml, so there’d have to be a registrator bug for this to hit General at this time. So at least it can’t just be user-error. Agreed it’s a good check to have though.
I think it's fine to add the check even if we assume that Registrator always do it correctly. We have some other checks (e.g. the list of files modified in a PR) that similarly should never fail on Registrator PR, but we still check it just as a internal consistency check.
In addition to possibly catching Registrator bugs this is a useful consistency check for people who run RegistryCI on their own registries, which may get PRs from other sources.
Nothing good will come if the registered version number does not match the version number in
Project.toml
in the given treehash. That these are consistent should be verified and should be easy to do as part of the "code can be loaded" check.The text was updated successfully, but these errors were encountered: