This is an automated email from the ASF dual-hosted git repository.
pcongiusti pushed a change to tag v2.6.0
in repository https://gitbox.apache.org/repos/asf/camel-k.git
*** WARNING: tag v2.6.0 was modified! ***
from c8657002f (commit)
to 628d08a28 (commit)
discard c8657002f chore(release): preparing 2.6.0
add b6a283a24 fix(release): push staging images
add 5d95dbcd4 chore(release): Helm chart for 2.6.0
new 628d08a28 chore(release): preparing for tag v2.6.0
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 (c8657002f)
\
N -- N -- N refs/tags/v2.6.0 (628d08a28)
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:
docs/charts/camel-k-2.6.0.tgz | Bin 236464 -> 236464 bytes
docs/charts/index.yaml | 6 +++---
.../bases/camel-k.clusterserviceversion.yaml | 2 +-
pkg/util/defaults/defaults.go | 4 ++--
script/Makefile | 13 +++++++++++--
script/git_tag.sh | 8 +++++---
6 files changed, 22 insertions(+), 11 deletions(-)
