Run CI against both :latest and :dev images#151
Merged
Conversation
purcell
force-pushed
the
ci-with-latest-and-dev
branch
from
14c307a to
25728a2
Compare
purcell
force-pushed
the
ci-with-latest-and-dev
branch
from
25728a2 to
f244aee
Compare
Collaborator
Author
|
fyi @alexrashed |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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 want to catch regressions as soon as possible to avoid unplanned disruption, which means explicitly running CI against both
latestanddev.(It turned out
localstackCLI was still defaulting to:dev, which we are fixing separately.)