@jdblischak This is to follow up on the workaround added in #322.

Now future 1.49.0 hits CRAN, I wonder if it fixes the check problem introduced by future 1.40.0.

If so, we should revert the GitHub Actions workflow change introduced in #322.