Publish helm chart script should not modify the chart content

[khorshuheng]

Which issue(s) this PR fixes:
The current publish helm chart script modifies the existing charts in the repository before publishing the chart. The original intention is that, should a developer forgot to update the version, the script will automatically correct the mistake.

However, this preprocessing is currently modifying the versions of the non-feast dependencies. As a result the helm chart publication job will fail due to dependency not being met (eg. Prometheus).

This PR remove the preprocessing step. Instead the developer should explicitly update the image/tag version in the release branch.

Does this PR introduce a user-facing change?:

NONE

[feast-ci-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: khorshuheng, woop

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details

Needs approval from an approver in each of these files:

• OWNERS [khorshuheng,woop]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[woop]

/lgtm

[feast-ci-bot]

@khorshuheng: Updated the config configmap in namespace default at cluster default using the following files:

• key config.yaml using file .prow/config.yaml

Details

In response to this:

Which issue(s) this PR fixes:
The current publish helm chart script modifies the existing charts in the repository before publishing the chart. The original intention is that, should a developer forgot to update the version, the script will automatically correct the mistake.

However, this preprocessing is currently modifying the versions of the non-feast dependencies. As a result the helm chart publication job will fail due to dependency not being met (eg. Prometheus).

This PR remove the preprocessing step. Instead the developer should explicitly update the image/tag version in the release branch.

Does this PR introduce a user-facing change?:

NONE

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.