This is an automated email from the ASF dual-hosted git repository.
github-bot pushed a change to tag v2.6.0-nightly
in repository https://gitbox.apache.org/repos/asf/camel-k.git
*** WARNING: tag v2.6.0-nightly was modified! ***
from 201d532cc (commit)
to 540455d78 (commit)
discard 201d532cc chore(ci): v2.6.0-nightly release updates
add 75878ef0c chore: starting release branch for release-2.6.x
add b6a283a24 fix(release): push staging images
add 5d95dbcd4 chore(release): Helm chart for 2.6.0
add 5ba7a098f fix(release): include constant changes
new 540455d78 chore(ci): v2.6.0-nightly release updates
This update added new revisions after undoing existing revisions.
That is to say, some revisions that were in the old version of the
tag 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 (201d532cc)
\
N -- N -- N refs/tags/v2.6.0-nightly (540455d78)
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 1 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/nightly-automatic-updates.yml | 2 +-
.github/workflows/nightly-release.yml | 2 +-
docs/charts/camel-k-2.6.0-nightly.tgz | Bin 236470 -> 236470 bytes
docs/charts/camel-k-2.6.0.tgz | Bin 0 -> 236464 bytes
docs/charts/index.yaml | 33 +++++++++++++++++++--
.../bases/camel-k.clusterserviceversion.yaml | 2 +-
script/Makefile | 13 ++++++--
script/git_tag.sh | 8 ++---
8 files changed, 48 insertions(+), 12 deletions(-)
create mode 100644 docs/charts/camel-k-2.6.0.tgz
