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_tomee-10.x
in repository https://gitbox.apache.org/repos/asf/tomee.git
discard 26d953c263 Minor: Regenerated BOMs for
93541579fb2a9a2cfb883dfca0ae229958b577e3
add 99fcfce22d [tomee-10.x]: Bump joda-time:joda-time from 2.14.2 to
2.14.3 (#2881)
add cc015630b6 Minor: Regenerated BOMs for
99fcfce22d5c05f3535a40424d7585eeee6fd805
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 (26d953c263)
\
N -- N -- N
refs/heads/regenerate_boms_after_dep_upgrade_tomee-10.x (cc015630b6)
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 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
