This is an automated email from the ASF dual-hosted git repository.
github-actions[bot] pushed a change to branch regenerate_boms_after_dep_upgrade
in repository https://gitbox.apache.org/repos/asf/tomee.git
discard 87d488516c Minor: Regenerated BOMs for
cb18d7746abedb5316c81e6b73ee664e2aa9b35a
add fb9c49acdf Bump org.apache.maven.plugins:maven-plugin-plugin from
3.15.2 to 3.16.0 (#3018)
add abbfe14163 Bump org.bouncycastle:bcmail-jdk18on from 1.85 to 1.86
(#3033)
add 28d635d661 Bump joda-time:joda-time from 2.14.3 to 2.15.0 (#3031)
add 83ffe6efca Minor: Regenerated BOMs for
28d635d661808240f36bb86bed9f133e777ac595
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 (87d488516c)
\
N -- N -- N refs/heads/regenerate_boms_after_dep_upgrade
(83ffe6efca)
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:
.../arquillian-tomee-tests/arquillian-tomee-jaxws-tests/pom.xml | 4 ++--
maven/pom.xml | 4 ++--
server/openejb-client/pom.xml | 2 +-
tomee/tomee-embedded/pom.xml | 2 +-
4 files changed, 6 insertions(+), 6 deletions(-)
