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 9c656b60fb Minor: Regenerated BOMs for
00dfd5a60b52c23580f40b1e8f31791534c36454
add 49e52593e2 Bump org.apache.maven.plugins:maven-release-plugin from
3.3.0 to 3.3.1
add 2b19a037ed Minor: Regenerated BOMs for
49e52593e28133ed40b34fb337a4cf7685bdfe0e
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 (9c656b60fb)
\
N -- N -- N refs/heads/regenerate_boms_after_dep_upgrade
(2b19a037ed)
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(-)
