This is an automated email from the ASF dual-hosted git repository.
github-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 48bd4e0728 Minor: Regenerated BOMs for
34bd7ea6e916c8872637c68f13c8123f1a70eacb
add f03e417ffc [tomee-10.x]: Bump org.apache:apache from 35 to 37
add 7d2585dba0 Minor: Regenerated BOMs for
f03e417ffce6601e5c31c0315271b35b56bde6df
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 (48bd4e0728)
\
N -- N -- N
refs/heads/regenerate_boms_after_dep_upgrade_tomee-10.x (7d2585dba0)
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(-)
