Update tools used in CI #25
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Hello I prefer having any CI deps that get a secret pinned to exact version instead of a tag/branch which can change. Would that be a problem to keep it that way (I'm OK with bumping it to a newer version, just taking the exact commit the v3 is at now)? |
This should fix the `coverage` job.
sandhose
force-pushed
the
quenting/fix-ci
branch
from
43f0630
to
91c186a
Compare
Makes sense! I did that in 91c186a |
|
Thank you (and sorry for the longer response time) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This updates all the GitHub Actions used in CI, and switches to using maintained actions where possible.
This should fix the
coveragejob from failing, and remove the warning about theset-outputcommand being deprecated.I would also suggest removing the
betaandnightlyjobs from the test matrix to reduce the number of jobs. This currently uses almost 50 jobs, which seems a bit overkill. Dropping those would drop that number to ~20. If you consider that a free personal plan includes 20 concurrent runners for the whole account, this would considerably speed up CI.