This is an automated email from the ASF dual-hosted git repository.
github-bot pushed a change to branch dependabot/maven/bytebuddy.version-1.18.5
in repository https://gitbox.apache.org/repos/asf/shiro.git
discard 79b3c72b7 chore(deps): bump bytebuddy.version from 1.18.4 to 1.18.5
add 0417dfa12 chore(deps): bump ch.qos.logback:logback-core from 1.5.28 to
1.5.32
add 10b8449c7 Merge pull request #2573 from
apache/dependabot/maven/ch.qos.logback-logback-core-1.5.32
add 7500b2618 chore(deps): bump ch.qos.logback:logback-classic from 1.5.28
to 1.5.32
add 7f1c62fe9 Merge pull request #2572 from
apache/dependabot/maven/ch.qos.logback-logback-classic-1.5.32
add c769a8fb3 chore(deps): bump github/codeql-action in the
github-dependencies group
add f80c9fa5f Merge pull request #2564 from
apache/dependabot/github_actions/github-dependencies-f7e9886b4e
add 48cc63a75 chore(deps): bump org.codehaus.gmavenplus:gmavenplus-plugin
add f0c355b76 Merge pull request #2566 from
apache/dependabot/maven/org.codehaus.gmavenplus-gmavenplus-plugin-4.3.1
add a72be978c chore(deps): bump bytebuddy.version from 1.18.4 to 1.18.5
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 (79b3c72b7)
\
N -- N -- N refs/heads/dependabot/maven/bytebuddy.version-1.18.5
(a72be978c)
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 | 4 ++--
.github/workflows/scorecards.yml | 2 +-
pom.xml | 6 +++---
3 files changed, 6 insertions(+), 6 deletions(-)
