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 3c552ce0f (commit) to fd077e9c2 (commit) discard 3c552ce0f chore(ci): v2.6.0-nightly release updates add 27d8eb0ef Update ingress.go add d85501375 chore: nightly automatic updates new fd077e9c2 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 (3c552ce0f) \ N -- N -- N refs/tags/v2.6.0-nightly (fd077e9c2) 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-nightly.tgz | Bin 236474 -> 236478 bytes docs/charts/index.yaml | 6 +- docs/modules/ROOT/partials/apis/camel-k-crds.adoc | 2 +- docs/modules/traits/pages/ingress.adoc | 2 +- helm/camel-k/crds/camel-k-crds.yaml | 70 ++++++++++----------- pkg/apis/camel/v1/trait/ingress.go | 2 +- .../camel.apache.org_integrationplatforms.yaml | 20 +++--- .../camel.apache.org_integrationprofiles.yaml | 20 +++--- .../crd/bases/camel.apache.org_integrations.yaml | 20 +++--- .../config/crd/bases/camel.apache.org_pipes.yaml | 10 +-- .../bases/camel-k.clusterserviceversion.yaml | 2 +- 11 files changed, 77 insertions(+), 77 deletions(-)