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 f87081f750 Disable MicroProfile Fault Tolerance tests due to #6285
discard 96f703bd59 Upgrade Quarkus to 3.14.0.CR1
add 5039103505 Bump io.quarkiverse.artemis:quarkus-artemis-bom from 3.3.0
to 3.4.0
add 1ff0bd4a68 Remove redundant generate JVM extension workflow
add 9e242ee44a Exclude most .github directory content from triggering core
CI workflows
add c6e63058ac Use markdown admonitions for dependabot branch sync warning
message
new 27c66e2e8e Upgrade Quarkus to 3.14.0.CR1
new 877fbf5c3e Disable MicroProfile Fault Tolerance tests due to #6285
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 (f87081f750)
\
N -- N -- N refs/heads/quarkus-main (877fbf5c3e)
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 2 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/ci-build.yaml | 20 ++++++
.github/workflows/generate-jvm-extension.yaml | 83 ----------------------
.github/workflows/pr-validate.yml | 10 +++
.../workflows/synchronize-dependabot-branch.yaml | 2 +-
pom.xml | 2 +-
5 files changed, 32 insertions(+), 85 deletions(-)
delete mode 100644 .github/workflows/generate-jvm-extension.yaml
