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 82ff750795 Minor: Regenerated BOMs for
abbfe141637cdb4b9c39283ed27bdf1735a1a0e0
add 28d635d661 Bump joda-time:joda-time from 2.14.3 to 2.15.0 (#3031)
add 908d0b390f Bump org.slf4j:slf4j-simple from 2.0.18 to 2.0.20 (#3026)
add 5bb7440cb4 Minor: Regenerated BOMs for
908d0b390f816ba2f27f76291bc3002c3bc0bdb2
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 (82ff750795)
\
N -- N -- N refs/heads/regenerate_boms_after_dep_upgrade
(5bb7440cb4)
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 ++--
arquillian/ziplock/pom.xml | 2 +-
2 files changed, 3 insertions(+), 3 deletions(-)
