Update github actions to latest versions #1680
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
Getting deprecation warnings, so time to upgrade.
misl6
reviewed
Sep 9, 2023
.github/workflows/pypi-release.yml
Outdated
| - name: Set up Python 3.x | ||
| uses: actions/setup-python@v2 | ||
| uses: actions/setup-python@v3 |
There was a problem hiding this comment.
Any reason to not use actions/setup-python@v4 ?
There was a problem hiding this comment.
My best guess: When I looked up the latest version number, and noted it down wrong, I wasn't wearing my glasses or the sun was in my eyes or I was drunk. :-( Sorry.
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.
In the various YAML files, the Github actions are locked to particular versions.
Some actions are out of date and are causing deprecation annotations. e.g.:
This PR updates all of the actions to the latest.
I briefly looked for any changes that affected this CI, but I didn't find any, which was as expected.