We had been using cran.microsoft.com for "interior" R versions. CRAN itself maintains repositories for "major" R versions (e.g. 4.2), but in the current minor version development cycle (4.2.0, 4.2.1, 4.2.3, 4.2.3 ...) CRAN only keeps packages built for the latest minor release. We had been using the Microsoft CRAN archive to load packages from the last date in which the minor release was updated. Since the Microsoft archive is going away, we'll retreat to just using the major-version CRAN, which will lead to occasional (but typically harmless) messages about (e.g.) packages having been built for R 4.2.3 when you're building an R 4.2.2 version of VisionEval.
I'll update the table of supported R versions to address that change.
jrawbits
commented
1 year ago
Per this document: https://techcommunity.microsoft.com/t5/azure-sql-blog/microsoft-r-application-network-retirement/ba-p/3707161 Microsoft is retiring their venerable CRAN archive (with daily snapshots of CRAN going back to 2014).
We had been using cran.microsoft.com for "interior" R versions. CRAN itself maintains repositories for "major" R versions (e.g. 4.2), but in the current minor version development cycle (4.2.0, 4.2.1, 4.2.3, 4.2.3 ...) CRAN only keeps packages built for the latest minor release. We had been using the Microsoft CRAN archive to load packages from the last date in which the minor release was updated. Since the Microsoft archive is going away, we'll retreat to just using the major-version CRAN, which will lead to occasional (but typically harmless) messages about (e.g.) packages having been built for R 4.2.3 when you're building an R 4.2.2 version of VisionEval.
I'll update the table of supported R versions to address that change.