This is an automated email from the ASF dual-hosted git repository. github-bot pushed a change to tag v2.6.1-nightly in repository https://gitbox.apache.org/repos/asf/camel-k.git
*** WARNING: tag v2.6.1-nightly was modified! *** from 37c3278ba (commit) to dac397711 (commit) discard 37c3278ba chore(ci): v2.6.1-nightly release updates new dac397711 chore(ci): v2.6.1-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 (37c3278ba) \ N -- N -- N refs/tags/v2.6.1-nightly (dac397711) 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.1-nightly.tgz | Bin 236553 -> 236550 bytes docs/charts/index.yaml | 6 +++--- .../bases/camel-k.clusterserviceversion.yaml | 2 +- 3 files changed, 4 insertions(+), 4 deletions(-)