This is an automated email from the ASF dual-hosted git repository.

dependabot[bot] pushed a change to branch 
dependabot/docker/config-ui/docker-patch-201b72f800
in repository https://gitbox.apache.org/repos/asf/devlake.git


 discard f0fbf227c build(deps): bump nginxinc/nginx-unprivileged
     add 928834f8d fix(ci): use default-days key for Dependabot cooldown (#9263)
     add c63d21d44 fix(docker): upgrade OS packages in release images (#9264)
     add 56a5efe4d build(deps): bump nginxinc/nginx-unprivileged

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   (f0fbf227c)
            \
             N -- N -- N   
refs/heads/dependabot/docker/config-ui/docker-patch-201b72f800 (56a5efe4d)

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/dependabot.yml | 2 +-
 backend/Dockerfile     | 2 ++
 config-ui/Dockerfile   | 7 ++++++-
 grafana/Dockerfile     | 4 +++-
 4 files changed, 12 insertions(+), 3 deletions(-)

Reply via email to