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 2a04af77f1 Minor: Regenerated BOMs for
5fea28af95930af3d1e16d71bdbf905ee1290ce3
add fcf6fee00c Bump org.glassfish:jakarta.faces from 4.0.13 to 4.0.14
new 2769638317 Minor: Regenerated BOMs for
fcf6fee00ca3b8c35d43499d7f27c03c51e78461
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 (2a04af77f1)
\
N -- N -- N refs/heads/regenerate_boms_after_dep_upgrade
(2769638317)
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.
The 1 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails. The revisions
listed as "add" were already present in the repository and have only
been added to this reference.
Summary of changes:
boms/tomee-plume-api/pom.xml | 2 +-
boms/tomee-plume/pom.xml | 2 +-
pom.xml | 2 +-
3 files changed, 3 insertions(+), 3 deletions(-)
