This is an automated email from the ASF dual-hosted git repository.
dependabot[bot] pushed a change to branch
dependabot/github_actions/actions-minor-patch-c610afa91b
in repository https://gitbox.apache.org/repos/asf/devlake.git
omit ad04b79d1 build(deps): bump the actions-minor-patch group across 1
directory with 3 updates
add c0e103e6b fix(ci): make Dependabot gomod PRs tested and lint-clean
(#9197)
add 9b71603fd build(deps): bump postgres 18.4 -> 18.6 and oauth2-proxy to
v7.15.5 (#9198)
add 4cf8bf3a5 build(e2e): commit package-lock.json for the Playwright
suite (#9199)
add f5fb9c4b0 build(deps): bump the actions-minor-patch group across 1
directory with 3 updates
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 (ad04b79d1)
\
N -- N -- N
refs/heads/dependabot/github_actions/actions-minor-patch-c610afa91b (f5fb9c4b0)
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 | 5 ++--
.github/workflows/test-e2e.yml | 8 +++---
.github/workflows/test.yml | 6 ++--
backend/.golangci.yaml | 7 +++++
docker-compose-dev-mysql.yml | 2 +-
docker-compose-dev-postgresql.yml | 4 +--
e2e/package-lock.json | 58 +++++++++++++++++++++++++++++++++++++++
7 files changed, 78 insertions(+), 12 deletions(-)
create mode 100644 e2e/package-lock.json
