chore(deps): update deadline-cloud-test-fixtures requirement from ~= 0.3.0 to == 0.4.* #75
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.
What was the problem/requirement? (What/Why)
The
deadline-cloud-test-fixtures
version0.4.0
was just released with a fix to adopt a breakingCreateFleet
API change.What was the solution? (How)
Bumps our pinned version to adopt
deadline-cloud-test-fixtures == 0.4.*
.What is the impact of this change?
The Worker Agent integration tests are unblocked from
CreateFleet
API errors.How was this change tested?
In aws-deadline/deadline-cloud-test-fixtures#35, the changes were tested by running the test fixtures locally using the docker container. This relies on that same testing.
Was this change documented?
No
Is this a breaking change?
No