This is an automated email from the ASF dual-hosted git repository.
github-bot pushed a change to branch
dependabot/maven/org.apache.rat-apache-rat-plugin-0.18
in repository https://gitbox.apache.org/repos/asf/camel-kamelets.git
discard 365be1323 chore(deps-dev): bump org.apache.rat:apache-rat-plugin from
0.17 to 0.18
add 949c0a9a7 Update google-mail-source expected header count to 9 (#2775)
add c40dbfb88 Regen for commit 949c0a9a740e5a4007fe39129e81e42975612910
(#2770)
add cb0f898e6 chore(deps): bump org.codehaus.plexus:plexus-utils from
4.0.2 to 4.0.3 (#2779)
add d8416da7f chore(deps): bump actions/setup-go from 6.3.0 to 6.4.0
(#2778)
add 8342039ad chore(deps): bump org.codehaus.plexus:plexus-utils (#2776)
add 7040e8248 chore(deps-dev): bump org.apache.rat:apache-rat-plugin from
0.17 to 0.18
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 (365be1323)
\
N -- N -- N
refs/heads/dependabot/maven/org.apache.rat-apache-rat-plugin-0.18 (7040e8248)
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:
.github/workflows/main-push-regen.yaml | 2 +-
.github/workflows/validate.yaml | 2 +-
.../java/org/apache/camel/kamelets/catalog/KameletsCatalogTest.java | 2 +-
.../src/main/resources/kamelets/databricks-sink.kamelet.yaml | 2 +-
.../src/main/resources/kamelets/databricks-source.kamelet.yaml | 2 +-
library/kamelets-maven-plugin/pom.xml | 2 +-
6 files changed, 6 insertions(+), 6 deletions(-)
