This is an automated email from the ASF dual-hosted git repository.
github-bot pushed a change to branch
dependabot/maven/org.apache.meecrowave-meecrowave-core-jakarta-1.2.15
in repository https://gitbox.apache.org/repos/asf/shiro.git
omit 2c4d71a2 Bump meecrowave-core from 1.2.14 to 1.2.15
add 988d4002 Bump versions-maven-plugin from 2.14.1 to 2.14.2
add 855397b4 Merge pull request #669 from
apache/dependabot/maven/org.codehaus.mojo-versions-maven-plugin-2.14.2
add 1f7fb125 Bump tomcat.version from 10.0.27 to 10.1.5
add 6e98488b Merge pull request #670 from
apache/dependabot/maven/tomcat.version-10.1.5
add d27ffc7b Bump meecrowave-core from 1.2.14 to 1.2.15
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 (2c4d71a2)
\
N -- N -- N
refs/heads/dependabot/maven/org.apache.meecrowave-meecrowave-core-jakarta-1.2.15
(d27ffc7b)
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:
pom.xml | 2 +-
samples/web-jakarta/pom.xml | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
