Print installed Task version #258
Merged
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
This could be useful in case users don't specify an exact version (e.g. `3.x`) but want to know what version of Task their CI actually ran.
|
|
per1234
added
status: blocked
per1234
approved these changes
Dec 3, 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.
Currently, if users set a version range (e.g.
3.x) they have no way to understand what Task version their CI actually ran by looking only at its logs.Printing the installed version is something other similar tools do (e.g. actions/setup-go) and that can be very useful in case of debugging.
As an example, in arduino/arduino-cli#1576 it was hard to understand what broke the CI as from the logs it seemed that nothing had changed.