You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@tomee.apache.org by gi...@apache.org on 2024/08/12 18:17:33 UTC
(tomee) branch regenerate_boms_after_dep_upgrade updated (3c47c56bf6 -> 21fdff66da)
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
omit 3c47c56bf6 Minor: Regenerated BOMs for 98e41ef028fec3a2c716fde7039df8c8b8bd861e
add 2e37c795f8 Bump org.testcontainers:junit-jupiter from 1.19.6 to 1.20.1
add 21fdff66da Minor: Regenerated BOMs for 2e37c795f865ce557fa25c589e7b23ebcf843f18
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 (3c47c56bf6)
\
N -- N -- N refs/heads/regenerate_boms_after_dep_upgrade (21fdff66da)
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:
examples/security-openid/pom.xml | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)