This is an automated email from the ASF dual-hosted git repository.
github-bot pushed a change to tag v2.7.0-nightly
in repository https://gitbox.apache.org/repos/asf/camel-k.git
*** WARNING: tag v2.7.0-nightly was modified! ***
from 9d5655c54 (commit)
to 074a2e03c (commit)
discard 9d5655c54 chore(ci): v2.7.0-nightly release updates
omit 460c7ff6f chore: nightly automatic updates
omit d31740a5d chore(release): help identify helm chart
omit 9d5ef76d6 chore: spare some time skipping unit test
omit e9cdaac87 chore: checkout release before starting procedure
add 52595bec8 chore(release): Helm chart for 2.7.0
add 735ca6564 chore: nightly automatic updates
new 074a2e03c chore(ci): v2.7.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 (9d5655c54)
\
N -- N -- N refs/tags/v2.7.0-nightly (074a2e03c)
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.7.0-nightly.tgz | Bin 239048 -> 239050 bytes
docs/charts/camel-k-2.7.0.tgz | Bin 0 -> 239045 bytes
docs/charts/index.yaml | 33 ++++++++++++++++++++++++++++++---
release.adoc | 7 ++-----
4 files changed, 32 insertions(+), 8 deletions(-)
create mode 100644 docs/charts/camel-k-2.7.0.tgz
