This is an automated email from the ASF dual-hosted git repository.
github-bot pushed a change to branch dependabot/maven/junit.version-5.13.0
in repository https://gitbox.apache.org/repos/asf/shiro.git
omit 73e9f55a5 chore(deps): bump junit.version from 5.12.2 to 5.13.0
add a68f670b6 chore(deps): bump ossf/scorecard-action from 2.4.1 to 2.4.2
add 694effc54 Merge pull request #2120 from
apache/dependabot/github_actions/ossf/scorecard-action-2.4.2
add 50ca4f022 chore(deps-dev): bump junit.engine.version from 1.12.2 to
1.13.0
add 7b39d2470 Merge pull request #2121 from
apache/dependabot/maven/junit.engine.version-1.13.0
add 610d93d99 chore(deps): bump junit.version from 5.12.2 to 5.13.0
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 (73e9f55a5)
\
N -- N -- N refs/heads/dependabot/maven/junit.version-5.13.0
(610d93d99)
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/scorecards.yml | 2 +-
support/spring-boot/pom.xml | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
