This is an automated email from the ASF dual-hosted git repository.
github-bot pushed a change to branch
dependabot/github_actions/github-dependencies-718fbf2243
in repository https://gitbox.apache.org/repos/asf/shiro.git
omit f4e647796 chore(deps): bump the github-dependencies group with 2
updates
add 2167c2fe7 chore: update dependency in RAT plugin to remove warnings on
JDK 25
add 18dc69fad chore: update maven wrapper to 3.3.4
add 3d08fe197 chore(maven-4): maven.properties -> maven-user.properties
add 83872f1e3 chore(deps): bump the github-dependencies group 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 (f4e647796)
\
N -- N -- N
refs/heads/dependabot/github_actions/github-dependencies-718fbf2243 (83872f1e3)
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/workflows/codeql.yml | 6 +--
.github/workflows/maven.yml | 4 +-
.github/workflows/pre-commit.yml | 2 +-
.github/workflows/scorecards.yml | 4 +-
.mvn/{maven.properties => maven-user.properties} | 0
.mvn/wrapper/maven-wrapper.properties | 20 +--------
mvnw | 50 ++++++++++++++++++---
mvnw.cmd | 56 ++++++++++++++++++++----
pom.xml | 15 ++++++-
9 files changed, 115 insertions(+), 42 deletions(-)
rename .mvn/{maven.properties => maven-user.properties} (100%)
