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_tomee-10.x
in repository https://gitbox.apache.org/repos/asf/tomee.git
discard 4b3a1dad73 Minor: Regenerated BOMs for
75c2b3eba63c4755f7dfd9c966629fa57a89ee0a
add 1f9e1497c8 [tomee-10.x]: Bump org.apache.felix:maven-bundle-plugin
from 6.1.0 to 6.2.0 (#3039)
add 8864c48792 [tomee-10.x]: Bump
org.codehaus.mojo:templating-maven-plugin from 3.1.0 to 3.1.1 (#3054)
add 7d0b264b38 Minor: Regenerated BOMs for
8864c4879275f0e4b1a869e1aa9f5acfdade0332
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 (4b3a1dad73)
\
N -- N -- N
refs/heads/regenerate_boms_after_dep_upgrade_tomee-10.x (7d0b264b38)
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:
itests/tomee-server-version/pom.xml | 2 +-
pom.xml | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
