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
discard 5b56e664f4 Minor: Regenerated BOMs for
fe7d6877c03ede1866da0b63152b04ea498737eb
add 3403b04924 Bump org.apache.httpcomponents.core5:httpcore5 from 5.4.3
to 5.4.4 (#2962)
add 69a0d68ebe Minor: Regenerated BOMs for
3403b04924d4badcdf88af5b75431bd448627f06
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 (5b56e664f4)
\
N -- N -- N refs/heads/regenerate_boms_after_dep_upgrade
(69a0d68ebe)
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:
tck/microprofile-tck/rest-client/pom.xml | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
