Pin Windows-compatible version of Task where necessary #185
Conversation
This file contains hidden or 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
The recent 3.9.1 release of the Task task runner does not correctly handle the PATH environment variable on Windows. Since the "template" workflows were configured to always use the latest version of Task within the 3.x major version series, this bug caused spurious failure of workflows under the following conditions: - Used a Windows runner - Ran a task that contained a command reliant on a file from PATH The workaround is to pin the version of Task used in these workflows to the last working version: 3.9.0.
per1234
added
type: imperfection
umbynos
approved these changes
Nov 30, 2021
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.
The recent 3.9.1 release of the Task task runner does not correctly handle the
PATHenvironment variable on Windows.Since the "template" workflows were configured to always use the latest version of Task within the 3.x major version
series, this bug caused spurious failure of workflows under the following conditions:
(example)
The workaround is to pin the version of Task used in these workflows to the last working version: 3.9.0.