[camel-k] branch dependabot/go_modules/github.com/spf13/viper-1.16.0 updated (e535e7ae3 -> decbdc5dc)

[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/github.com/spf13/viper-1.16.0
in repository https://gitbox.apache.org/repos/asf/camel-k.git


 discard e535e7ae3 chore(deps): bump github.com/spf13/viper from 1.15.0 to 1.16.0
     add 29f25676e Revert "feat(core): Fix Operator and Builder Pod user as non root 1000"
     add d7a6820f5 fix(core): Minimal configuration needed for S2I to work (root user on FS access for operator)
     add 6ddd07557 chore(deps): remove old replacements
     add decbdc5dc chore(deps): bump github.com/spf13/viper from 1.15.0 to 1.16.0

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   (e535e7ae3)
            \
             N -- N -- N   refs/heads/dependabot/go_modules/github.com/spf13/viper-1.16.0 (decbdc5dc)

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:
 build/Dockerfile                  |   6 +-
 go.mod                            |  10 -
 go.sum                            | 435 +-------------------------------------
 pkg/controller/build/build_pod.go |   8 +-
 pkg/install/operator.go           |  12 +-
 5 files changed, 16 insertions(+), 455 deletions(-)