How often are the CRAN mirror repositories updated?

[gwerbin]

I noticed that cran/ckmeans.1d.dp was updated to version 3.3 very quickly, but it has not been updated to 3.4 which came out shortly afterwards. Are the mirror repositories updated on a schedule? If so, what is that schedule? sorry if this is on the website and I missed it.

[gaborcsardi]

The package DB at crandb.r-pkg.org is updated every minute, but the website caches package data for one hour:

metacranweb/lib/cache.js

Lines 7 to 24 in 7723472

	'ghstars:': 60 * 60, // GitHub stars, 1 hour
	'news:': 60 * 60 * 5, // NEWS, 5 hours
	'package:': 60 * 60, // Package info, 1 hour
	'pkgtv:': 60 * 60 * 24, // Task views for a package, 1 day
	'readme:': 60 * 60 * 5, // Package README, 5 hours
	'revdeps:': 60 * 60, // Package reverse dependencies, 1 hour
	'index:num-active': 60 * 60, // # active pkgs, 1 hour
	'index:num-downloads': 60 * 60 * 24, // # downloads, 1 day
	'index:num-maint': 60 * 60, // # maintainers, 1 hour
	'index:num-updates': 60 * 60 * 24, // # updates last week
	'index:recent': 60 * 10, // # recent packages, 10 minutes
	'index:top-downloaded': 60 * 60 * 24, // top downloaded, 1 day
	'index:top-starred': 60 * 60 * 5, // top starred, 5 hours
	'index:trending': 60 * 60 * 24, // trending packages, 1 day
	'index:top-revdeps': 60 * 60, // most depended upon, 1 hour
	'list:top-depended': 60 * 60 * 24 // most depended upon

[gwerbin]

Thanks for the reply. What about the actual Git mirror repositories then? That's what I'm wondering about here, sorry if I wasn't clear.

[gaborcsardi]

In theory that also updates every minute, but in practice it sometimes fails.....

[timehat]

Any suggested mechanism to prompt for a re-sync in the event of a failure? (Current instance I'm looking at is the ChannelAttribution library which is at v1.16 on cran but the latest label on the Github mirror is 1.14: https://github.com/cran/ChannelAttribution/releases) Thank you for setting up these mirrors nonetheless!