This is an automated email from the ASF dual-hosted git repository.

mariofusco pushed a change to branch q3lts
in repository 
https://gitbox.apache.org/repos/asf/incubator-kie-kogito-runtimes.git


 discard c24f3ccbe6 wip
 discard 025211769e wip
 discard 0c56856225 wip : fix jakarta.validation-api version
 discard 7502f6b171 Apply patches
 discard 5bb12cc41f fixed quarkus3 patches
 discard 6d01db12a6 [Quarkus 3] Updated rewrite data
 discard 4c14480806 Bump to Quarkus 3.2.9.Final
     add 48a2ccc7f9 Update version to Kogito 2.0.0-SNAPSHOT / Drools 
8.46.0-SNAPSHOT
     new 4755322042 Bump to Quarkus 3.2.9.Final
     new 3158578c68 [Quarkus 3] Updated rewrite data
     new a55c8ae75a fixed quarkus3 patches
     new d5e21883c5 Apply patches
     new 4cb2899623 wip : fix jakarta.validation-api version
     new 4c0a4f1a7d wip
     new 7f22624621 wip

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   (c24f3ccbe6)
            \
             N -- N -- N   refs/heads/q3lts (7f22624621)

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 7 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:
 kogito-build/kogito-kie-bom/pom.xml | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to