This is an automated email from the ASF dual-hosted git repository.
github-bot pushed a change to branch
dependabot/npm_and_yarn/airavata-local-agent/next-15.2.4
in repository https://gitbox.apache.org/repos/asf/airavata.git
discard 6f565bfbb2 Bump next from 13.5.6 to 15.2.4 in /airavata-local-agent
add c01b7d70ae Bump vite from 6.2.1 to 6.2.7 in
/modules/research-framework/portal
add 9c9e697d2d Bump tar-fs and dockerode in /airavata-local-agent
add 43ae938659 Bump jinja2 from 3.1.1 to 3.1.6 in /dev-tools/ansible
add 81cb3e163c Bump json in /airavata-services/services-security
add d7e276a5c4 Bump next from 13.5.6 to 15.2.4 in /airavata-local-agent
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 (6f565bfbb2)
\
N -- N -- N
refs/heads/dependabot/npm_and_yarn/airavata-local-agent/next-15.2.4 (d7e276a5c4)
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:
airavata-local-agent/package-lock.json | 22033 +++++++++++++++----
airavata-local-agent/package.json | 2 +-
airavata-services/services-security/pom.xml | 2 +-
dev-tools/ansible/requirements.txt | 2 +-
.../research-framework/portal/package-lock.json | 4350 +++-
modules/research-framework/portal/package.json | 2 +-
6 files changed, 21093 insertions(+), 5298 deletions(-)
