[apisix-ingress-controller] branch dependabot/go_modules/test/e2e/github.com/stretchr/testify-1.8.4 updated (fe0cd572 -> 208cc908)

[gi...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

github-bot pushed a change to branch dependabot/go_modules/test/e2e/github.com/stretchr/testify-1.8.4
in repository https://gitbox.apache.org/repos/asf/apisix-ingress-controller.git


    omit fe0cd572 chore(deps): bump github.com/stretchr/testify in /test/e2e
     add 32c07516 Update issuer.yaml (#1856)
     add 8e86331c docs: update docs links (#1873)
     add a79c1404 chore(deps): bump k8s.io/client-go from 0.27.1 to 0.27.3 in /test/e2e (#1866)
     add 208cc908 chore(deps): bump github.com/stretchr/testify in /test/e2e

This update added new revisions after undoing existing revisions.
That is to say, some revisions that were in the old version of the
branch 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   (fe0cd572)
            \
             N -- N -- N   refs/heads/dependabot/go_modules/test/e2e/github.com/stretchr/testify-1.8.4 (208cc908)

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.

No new revisions were added by this update.

Summary of changes:
 docs/en/latest/config.json                          | 21 +++++++++++++++++----
 docs/en/latest/tutorials/cert-manager/issuer.yaml   |  2 +-
 ...istio-egress-gateway => istio-egress-gateway.md} |  0
 test/e2e/go.mod                                     |  6 +++---
 test/e2e/go.sum                                     | 12 ++++++------
 5 files changed, 27 insertions(+), 14 deletions(-)
 rename docs/en/latest/tutorials/{istio-egress-gateway => istio-egress-gateway.md} (100%)