I'm guessing this is straightforward to do in a GH action yml file, but I haven't checked yet. ...
@seankross seem wise?
e.g, we just made a new release of rcromwell, but that new metadata won't be updated until the cron schedule is hit.
We don't include package version or release number in the registry anyway I guess, but probably should (e.g., would be good to show latest pkg version or release (which should be the same) on our wilds pkgs page
I'm guessing this is straightforward to do in a GH action yml file, but I haven't checked yet. ...
@seankross seem wise?
e.g, we just made a new release of
rcromwell, but that new metadata won't be updated until the cron schedule is hit.We don't include package version or release number in the registry anyway I guess, but probably should (e.g., would be good to show latest pkg version or release (which should be the same) on our wilds pkgs page