This is an automated email from the ASF dual-hosted git repository.
github-bot pushed a change to branch regen_bot_sbom
in repository https://gitbox.apache.org/repos/asf/camel-kamelets.git
omit 7d52cd3c Regen SBOM from commit
bdeb394dc7a846f078760376492f7ae0234677d1
add b6510478 Regen SBOM from commit
bdeb394dc7a846f078760376492f7ae0234677d1
add e1868a43 Updated CHANGELOG.md
add d823d0bd Azure Storage Blob Kamelets: Expose the credentialsType
parameter with SHARED_ACCOUNT_KEY as default
add 8933c7e6 Updated CHANGELOG.md
add 9ee9ff97 Updated CHANGELOG.md
add 38607fe0 Regen SBOM from commit
9ee9ff972ea7af2c274172ad04a421294a77f851
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 (7d52cd3c)
\
N -- N -- N refs/heads/regen_bot_sbom (38607fe0)
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:
CHANGELOG.md | 17 +++++++++++++++--
camel-kamelets-sbom/camel-kamelets-sbom.json | 4 ++--
camel-kamelets-sbom/camel-kamelets-sbom.xml | 4 ++--
kamelets/azure-storage-blob-sink.kamelet.yaml | 11 ++++++++---
kamelets/azure-storage-blob-source.kamelet.yaml | 15 ++++++++++-----
.../kamelets/azure-storage-blob-sink.kamelet.yaml | 11 ++++++++---
.../kamelets/azure-storage-blob-source.kamelet.yaml | 15 ++++++++++-----
7 files changed, 55 insertions(+), 22 deletions(-)
