I have had to remove at least three or four packages from this repo in total because they were removed from CRAN and so the CI pipeline would be unable to find the package. These packages are still available in the CRAN archive and a user or a manifest could potentially still install an old version of them, but when we remove the install script, we still break the application.
I think a more gentle solution that could benefit users who have pinned old dependencies is to mark certain packages as unsupported, causing CI to skip them but still allowing them to keep doing what they always did in case a user managed to install an archived version of the package.
I have had to remove at least three or four packages from this repo in total because they were removed from CRAN and so the CI pipeline would be unable to find the package. These packages are still available in the CRAN archive and a user or a manifest could potentially still install an old version of them, but when we remove the install script, we still break the application.
I think a more gentle solution that could benefit users who have pinned old dependencies is to mark certain packages as unsupported, causing CI to skip them but still allowing them to keep doing what they always did in case a user managed to install an archived version of the package.