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.
Before this PR
The previous behavior of
docker push
was to push all tags of a given image. This changed recently wheredocker push
will just push thelatest
tag per default (see: moby/moby#40302, docker/cli#2220).A bunch of users relied on having the
./gradlew dockerPush
task as a default task for pushing all tags and are now no longer publishing all tags.After this PR
The
dockerPush
task is now an alias for thedockerTagsPush
task and will push all available tags per default.==COMMIT_MSG==
Docker push pushes all tags
==COMMIT_MSG==
Possible downsides?
Maybe we should instead migrate all users that rely on this feature to use
dockerTagsPush
instead ofdockerPush
and keep the current behavior?