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.
Fixes #1355
This switches from major version 1 to major version 2 of
taiki-e/install-action
to fix the new Windows failure described in #1355.For consistency, and because it is preferable to use new versions over very old versions provided they are stable and there is no known reason to prefer the much older version, this changes it in both job definitions that use it, even though the problem only occurs in one generated job (the Windows job) from one of the job definitions (the other one does not generate a Windows job).
However, this is not a general GitHub Action upgrading PR. It is intended to make the minimal change, of those that seem both reasonable and non-confusing, to fix that issue and allow CI checks to pass again. Although I think it would be good to use later versions of some other actions, some of which are quite old, I think that automating such upgrades should be considered, and my inclination is to regard that decision beyond the scope of this PR. But see #1357.
As a demonstration that #1355 really does affect his upstream repository and thus needs fixing--since when I originally opened that I had only produced it in my fork--see this failing job in #1357. No corresponding failure happens here, even though the job does run here, because this PR fixes the issue.