This is an automated email from the ASF dual-hosted git repository.
github-bot pushed a change to branch
dependabot/maven/mailreader2/commons-beanutils-commons-beanutils-1.11.0
in repository https://gitbox.apache.org/repos/asf/struts-examples.git
discard c1b6bc3 Build(deps): Bump commons-beanutils:commons-beanutils in
/mailreader2
add 5eacfb3 Build(deps): Bump shiro.version from 2.0.3 to 2.0.4
add f39f6ee Merge pull request #449 from
apache/dependabot/maven/shiro.version-2.0.4
add 9a6cbf1 Build(deps): Bump actions/cache from 4.2.3 to 4.2.4
add 4a7fdc8 Merge pull request #478 from
apache/dependabot/github_actions/actions/cache-4.2.4
add c4af40d Build(deps): Bump commons-beanutils:commons-beanutils in
/mailreader2
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 (c1b6bc3)
\
N -- N -- N
refs/heads/dependabot/maven/mailreader2/commons-beanutils-commons-beanutils-1.11.0
(c4af40d)
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/maven.yml | 2 +-
shiro-basic/pom.xml | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
