Well crap. A project from over 5 years ago, when I wasn't doing things well, and I've not got package versions recorded, and was doing all of the analysis via a `knitr` script, with very few intermediates saved.

And now collabs have reviewer comments, and want to change some outputs.

The package is under a git repo, but figuring out how far back to go is a pain in the butt.

So glad using `renv` now at least gives me a record of what versions I had at the time of analysis. #RStats

@rmflight I created a package with a function for this situation (if you have the session info or at least some versions recorded): https://llrs.github.io/repo.data/reference/cran_date.html

I hope you manage to continue the project and successfully answer the reviwers (and colleagues).

Estimate CRAN's date — cran_date

Check which CRAN dates are possible for a given packages and versions.

@rmflight It works even without known versions:

cran_date(versions = data.frame(Package = c("rversions", "rtoot"), Version = NA))
[1] "2022-11-11"

Which would be when these two packages are first on CRAN. Edit2: fixed typo. The function works correctly.

I'm working on making it work with Bioconductor packages (and version) but I think that just a date would be close enough.