This is an automated email from the ASF dual-hosted git repository.
github-bot pushed a change to branch regenerate_boms_after_dep_upgrade
in repository https://gitbox.apache.org/repos/asf/tomee.git
discard c732e5fb1a Minor: Regenerated BOMs for
c0dfb52a26b2e4e225f0b33dc7059835a5b453c7
add 8bcfb01d40 TOMEE-4384 Commons Compress 1.27.0
add 55b3d0364c Minor: Regenerated BOMs for
8bcfb01d403e5f283acad3f3f5aa17f5c915258e
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 (c732e5fb1a)
\
N -- N -- N refs/heads/regenerate_boms_after_dep_upgrade
(55b3d0364c)
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 +-
1 file changed, 1 insertion(+), 1 deletion(-)
