A few days ago I called registrator to register a new version of AD4SM from v0.06 to v0.07, after fixing a few issues the registrator terminated successfully with all check passed see here
but still juliapackages hold the last version from Aug 2019, see here, and if I try to update the package from the REPL I still get the old version
am I missing something, or did something wrong? where can I find instructions to on how to register a new version of a package ?
The registration wasn’t merged:
It would be purple instead of green and say “merged” if it was. So that means the registration is not completed yet.
Scrolling down, it was blocked by a comment:
You can tell by the label. Was that commentator you? If so you will want to delete those comments or edit them and add [noblock] to stop blocking registration.
Once the registration is merged, it will be registered and should be available from the REPL. I’m not sure how often https://juliapackages.com/ updates though, in the past it has sometimes not been reliably updated.
Thanks a lot! I just deleted that comment – I thought calling the registrator again would have overridden it.
Will it now proceed to register the new version automatically, or do I need to trigger it manually?
…
it says merged now, I should probably be OK, may thanks!
The ground truth for existing versions of your package is General/A/AD4SM/Versions.toml at master · JuliaRegistries/General · GitHub. Third party package sites update at their own schedule.
I can see why you’d think that, but it doesn’t work that way because if there was a legitimate third-party objection to the registration of some package, it wouldn’t be good if the author could bypass that block just by re-triggering registration.
On a technical level, there’s actually 2 separate pieces: the CI checks that run when the PR is pushed to (which is what re-triggering registration does), and a separate “merge check” that runs every 15 mins or so. That merge check loops through all PRs and sees if they are mergable. Any blocking comments disqualifies, as does failing CI, or not enough time having passed. If it’s eligible for merging, it gets merged.
So re-triggering registration causes the per-PR checks to rerun (maybe there was a compat bounds that was missing which was fixed, so it will check again), but doesn’t do anything for blocking comments.
Thanks a lot, that’s clear and makes perfect sense!
Sure. That said, the JuliaHub Web site is up-to-date in my experience. The page for AD4SM.jl shows the current version as v0.0.7.
