This is an automated email from the ASF dual-hosted git repository.
github-bot pushed a change to branch quarkus-main
in repository https://gitbox.apache.org/repos/asf/camel-quarkus.git
discard e0530a4473 Disable microprofile-fault-tolerance integration test
native profile due to #6584
discard cf74de9df6 Disable git native profile due to #6559
discard da36d42179 Disable UpdateExtensionDocPageMojo due to #6418
discard 338279ce80 Upgrade Quarkus to 3.16.0.CR1
add eb60b20da9 Bump actions/upload-artifact from 4.4.2 to 4.4.3 (#6621)
new 61dc6bf181 Upgrade Quarkus to 3.16.0.CR1
new 662a1ec5ec Disable UpdateExtensionDocPageMojo due to #6418
new a1c609fc24 Disable git native profile due to #6559
new e19c7d92f5 Disable microprofile-fault-tolerance integration test
native profile due to #6584
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 (e0530a4473)
\
N -- N -- N refs/heads/quarkus-main (e19c7d92f5)
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 4 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:
.github/workflows/camel-master-cron.yaml | 2 +-
.github/workflows/ci-build.yaml | 4 ++--
.github/workflows/quarkus-master-cron.yaml | 2 +-
3 files changed, 4 insertions(+), 4 deletions(-)
