This is an automated email from the ASF dual-hosted git repository.
dependabot[bot] pushed a change to branch
dependabot/pip/backend/python/pydevlake/python-minor-patch-211fd9af5c
in repository https://gitbox.apache.org/repos/asf/devlake.git
discard 53eecb268 build(deps): bump the python-minor-patch group across 2
directories with 2 updates
add d1e8aded5 build(deps): bump jsonpointer in /backend/python/pydevlake
(#9110)
add 69535edd2 build(deps): bump @testing-library/jest-dom in /config-ui
(#9114)
add 04ae22b4c build(deps): bump jsdom from 29.1.1 to 30.0.1 in /config-ui
(#9113)
add 36e3c0770 build(deps): bump @types/node from 24.13.2 to 26.4.1 in
/config-ui (#9112)
add 076db9641 build(deps): bump the python-minor-patch group across 2
directories with 2 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 (53eecb268)
\
N -- N -- N
refs/heads/dependabot/pip/backend/python/pydevlake/python-minor-patch-211fd9af5c
(076db9641)
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:
backend/python/pydevlake/poetry.lock | 12 +--
backend/python/pydevlake/pyproject.toml | 2 +-
config-ui/package.json | 6 +-
config-ui/yarn.lock | 178 ++++++++++++++++----------------
4 files changed, 100 insertions(+), 98 deletions(-)
