Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Specify maximum package version #882

Closed
ms609 opened this issue Jul 25, 2024 · 2 comments
Closed

Specify maximum package version #882

ms609 opened this issue Jul 25, 2024 · 2 comments

Comments

@ms609
Copy link
Contributor

ms609 commented Jul 25, 2024

Is your feature request related to a problem? Please describe.
I'd like to use 'testthat' to test a package on R 3.6, but the latest version of 'testthat' has a subdependency ('evaluate') that requires R4.0

Describe the solution you'd like
Ideally, the use the most recent version of a package that is compatible with the version of R being used.

Less ideally, manually specify a maximum version of a package for each testing environment

Describe alternatives you've considered
I think a maximum version of a package can be specified in the DESCRIPTION file, but this doesn't help if I also want to fully test the package against the latest version of R.

Possibly as in #727 I could specify a URL to a particular archived version of the package on CRAN – but this would require me to set up and maintain a separate workflow for each version of R, rather than using a simple matrix.

@gaborcsardi
Copy link
Member

Ideally, the use the most recent version of a package that is compatible with the version of R being used.

This is not possible with CRAN-like repositories.

Less ideally, manually specify a maximum version of a package for each testing environment

This is also not possible.

One solution that is certainly possible, is to duplicate the setup-r-dependencies step in your workflow, and specify a different testthat version for R 3.6.x.

Btw. setup-r-dependencies@v2 will also require R 4.0.0 at some point.

Copy link

This issue has been automatically locked. If you believe you have found a related problem, please file a new issue and include a link to this issue

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Aug 15, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants