Average/expected CRAN lag for crandb

[pat-s]

What is the expected lag behind CRAN package updates/additions for crandb?

In some projects where I am using pak::pkg_history(), which relies on crandb in the end AFAICS, I've lately noticed that the information returned sometimes lags more than 3-4 days behind CRAN.

While this is not an issue in the first place for the general use of the information, it would be good to know:

• What the expected lag of crandb is
• What a safe duration lag setting in production envs can be (which relates to the expected lag in the first place)

I.e. how many days back into I have to go to safely ensure the returned information shows the truth for the given date.

E.g., as of today, some packages from March 19th are lacking their most recent CRAN release (e.g. MDPIexploreR, which right now returns

tail(pak::pkg_history('MDPIexploreR'))
# A data frame: 1 × 21
  Package      Title    Version URL   `Authors@R` Description VignetteBuilder License Encoding RoxygenNote
* <chr>        <chr>    <chr>   <chr> <chr>       <chr>       <chr>           <chr>   <chr>    <chr>      
1 MDPIexploreR Web Scr… 0.2.0   http… "person(\"… Provides c… knitr           CC BY … UTF-8    7.3.2  

Even though 0.3.0 has been published on CRAN on 2025-03-19.

(I didn't go back in time further to find the exact lag date for today.)

[gaborcsardi]

It is updated here, normally hourly: https://github.com/metacran/cron/actions/runs/14011435514/workflow#L6