This is an automated email from the ASF dual-hosted git repository.
dependabot[bot] pushed a change to branch
dependabot/npm_and_yarn/gremlin-js/master/types/node-26.1.0
in repository https://gitbox.apache.org/repos/asf/tinkerpop.git
discard 3c21c075c2 build(deps-dev): bump @types/node from 25.6.0 to 26.1.0 in
/gremlin-js
add 994853b293 Fix JS dependency vulnerabilities via non-breaking lockfile
updates
add efbbc19c4a Merge branch '3.7-dev' into 3.8-dev
add 2ca64b04e1 Fix JS dependency vulnerabilities via non-breaking lockfile
updates
add 372e235be6 Merge branch '3.8-dev'
add 43e59bc17f Fix JS dependency vulnerabilities via non-breaking lockfile
updates
add a8440eb1a6 build(deps-dev): bump @types/node from 25.6.0 to 26.1.0 in
/gremlin-js
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 (3c21c075c2)
\
N -- N -- N
refs/heads/dependabot/npm_and_yarn/gremlin-js/master/types/node-26.1.0
(a8440eb1a6)
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:
docs/gremlator/package-lock.json | 382 ++++++++-------------
docs/gremlint/package-lock.json | 344 +++++++++----------
.../gremlin-javascript/package-lock.json | 12 +-
gremlin-js/package-lock.json | 6 +-
4 files changed, 300 insertions(+), 444 deletions(-)
