Overview
This is to be compatible with dfxvm once it's released.
I also updated all of the workflows to use actions/checkout@v4. This PR is split into two commits: the first updates to actions/checkout@v4, the second updates to use dfinity/setup-dfx.
Requirements
These tests should install dfx now, and after dfxvm is released.
Recommended Solution
There's a github action now, so it seems nice to use it. Also the workflows used to use a couple different methods of overriding the dfx version. Now there's just one:
Overview This is to be compatible with dfxvm once it's released.
I also updated all of the workflows to use actions/checkout@v4. This PR is split into two commits: the first updates to actions/checkout@v4, the second updates to use dfinity/setup-dfx.
Requirements These tests should install dfx now, and after dfxvm is released.
Considered Solutions Another option would have been to copy the path setup from https://github.com/dfinity/setup-dfx/blob/main/action.yml into the provision scripts.
Recommended Solution There's a github action now, so it seems nice to use it. Also the workflows used to use a couple different methods of overriding the dfx version. Now there's just one:
Considerations This should reduce maintenance costs going forward, since https://github.com/dfinity/setup-dfx should be able to perform its part.