This is an automated email from the ASF dual-hosted git repository.
alpinegizmo pushed a change to branch release-2.3-dockerfiles
in repository https://gitbox.apache.org/repos/asf/flink-docker.git
omit 4f354ec Update docker_push workflow for 2.3.0 release
omit 517999a Update snapshot workflow for 2.3.0 release
omit 9b48b77 Update Dockerfiles for 2.3.0 release
add 708ffc0 [hotfix] Bump setup-qemu-action to 4.1.0
add b234702 [hotfix] Bump setup-buildx-action to 4.0.0
add efbd32e [hotfix] Bump docker login action to 4.0.0
add eb9dd2b Update Dockerfiles for 2.3.0 release
add 9494048 Update snapshot workflow for 2.3.0 release
add 24e1a25 Update docker_push workflow for 2.3.0 release
This update added new revisions after undoing existing revisions.
That is to say, some revisions that were in the old version of the
branch are not in the new version. This situation occurs
when a user --force pushes a change and generates a repository
containing something like this:
* -- * -- B -- O -- O -- O (4f354ec)
\
N -- N -- N refs/heads/release-2.3-dockerfiles (24e1a25)
You should already have received notification emails for all of the O
revisions, and so the following emails describe only the N revisions
from the common base, B.
Any revisions marked "omit" are not gone; other references still
refer to them. Any revisions marked "discard" are gone forever.
No new revisions were added by this update.
Summary of changes:
.github/workflows/docker_push.yml | 6 +++---
.github/workflows/snapshot.yml | 6 +++---
2 files changed, 6 insertions(+), 6 deletions(-)