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
omit 1935d48793 Minor: Regenerated BOMs for
33ca5bd02ffeb0a67ee0a9c8a443a0c5712b2c5b
omit 33ca5bd02f Bump org.hibernate.validator:hibernate-validator from
9.1.3.Final to 9.1.4.Final (#3048)
add b807dec38a Minor: Regenerated BOMs for
4268dd644dd0b2730337cd57d6e26992af594c35
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 (1935d48793)
\
N -- N -- N refs/heads/regenerate_boms_after_dep_upgrade
(b807dec38a)
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(-)
