Fix condition for executing step getting upstream builds #219
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
We were using wrong input to detemine if the `Get upstream packages versions` step should be run. The `upstreamBuilds` is not boolean, we should have been using `useUpstreamBuilds` instead.
r-czajkowski
approved these changes
Sep 30, 2022
|
Preview uploaded to https://preview.dashboard.test.threshold.network/fix-manual-deployment/index.html. |
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.
We were using wrong input to determine if the
Get upstream packages versionsstep should be run. TheupstreamBuildsis not boolean, we should have been usinguseUpstreamBuildsinstead.Previous implementation was resulting in incorrect resolving of the versions, see command in
Resolve contractsstep in https://github.com/threshold-network/token-dashboard/actions/runs/3157088578/jobs/5137628670.