feat: automatically update the appVersion in Chart when release new version

[rajeshkio]

#547

What type of PR is this?

/kind feature

What this PR does / why we need it:

Governance: Automatically update the appVersion in the Chart when released

Which issue(s) this PR fixes:

Fixes #547

[rajeshkio]

I have raised this PR to test the changes. I couldn't find a better way to test it.

[elliotxx]

Yeah, I know. I will test it with you.

[rajeshkio]

Yeah, I know. I will test it with you.

Do you need to approve or something? Not seeing the workflow running.

[elliotxx]

@rajeshkio The pipeline need to be triggered by pushing a new tag. Let me test it.

[elliotxx]

It should be modify to steps.get_chart_version.outputs.new_chart_version, otherwise the version cannot be obtained.

[elliotxx]

There is also a strange error:
Error: failed to create PR: Error: could not parse file with path: /home/runner/work/karpor/karpor/charts/karpor/Chart.yaml
https://github.com/KusionStack/karpor/actions/runs/10465960133/job/28982008775

[rajeshkio]

Is there a way for me to test it without disturbing you?

[elliotxx]

@rajeshkio You can push the alpha tag to trigger the Release pipeline, just like this 👇. But I'm not sure if this will take effect in the fork repository.

[elliotxx]

There is also a strange error: Error: failed to create PR: Error: could not parse file with path: /home/runner/work/karpor/karpor/charts/karpor/Chart.yaml https://github.com/KusionStack/karpor/actions/runs/10465960133/job/28982008775

I think I know what this error is about. It need to first use checkout action to clone the charts repository locally.

You can reference to: https://github.com/fjogeleit/yaml-update-action?tab=readme-ov-file#advanced-example-with-an-separate-target-repository

[rajeshkio]

Thank you. Today I am a bit busy with office stuff. I will check it soon.

[elliotxx]

Yeah, If you need help, please ping me anytime.

[elliotxx]

Hi, I re-triggered the pipeline and found a new problem:

It seems that we should replace propertyPath with changes here:

[rajeshkio]

Thank you, but I need a concrete way to test it myself. This is not good, depending on you to find the problem and me just updating the code.

[elliotxx]

@rajeshkio Yeah, I know. The pipeline is triggered by tags. Have you tried pushing tags (such as v0.4.11-alpha.1) to your fork repository to see if the pipeline can be triggered.

[rajeshkio]

Do you mean git tag? I will try with the change

[rajeshkio]

I think it won't work with the fork repo. It didn't get the docker credentials

Run docker/login-action@v2
with:
ecr: auto
logout: true
Error: Username and password required

[elliotxx]

@rajeshkio OK, It seems that the pipeline can be triggered in the fork repository, and unrelated jobs can be deleted. Just keep the update-chart step.

[rajeshkio]

Sorry bit new to this workflow. You are saying for testing I can remove unrelated jobs and only keep the steps I need in .github/workflows/release.yaml? After testing revert back all the jobs?

[elliotxx]

@rajeshkio Yes, just for testing.

[rajeshkio]

Now it fails with httpError. I am doubting I GITHUB_TOKEN is available while running through fork repo. Can you test and let me know?

Run fjogeleit/yaml-update-action@main
with:
repository: KusionStack/charts
valueFile: charts/karpor/Chart.yaml
changes: {"version":"0.6.6", "appVersion":"v0.4.18-alpha.1"}
value: v0.4.18-alpha.1
branch: bump-karpor-to-v0.4.18-alpha.1
targetBranch: master
createPR: false
message: refactor: bump karpor version to v0.4.18-alpha.1
token: ***
workDir: charts
noCompatMode: false
quotingType: '
force: false
masterBranchName: master
githubAPI: https://api.github.com
commitChange: true
updateFile: false
labels: yaml-updates
commitUserName: github-actions[bot]
commitUserEmail: 41898282+github-actions[bot]@users.noreply.github.com
env:
GO_RELEASER_CONFIG: .goreleaser-dev.yml
Error: failed to create PR: HttpError: Resource not accessible by integration

[elliotxx]

@rajeshkio Yeah, let me try.

[elliotxx]

@rajeshkio I also encountered the same problem, maybe it's related to this:

Can you modify the target branch to chart-version-updater? Then I merged this PR, so that we can debug it in the upstream repo.

[rajeshkio]

@rajeshkio I also encountered the same problem, maybe it's related to this:

Can you modify the target branch to chart-version-updater? Then I merged this PR, so that we can debug it in the upstream repo.

Done

[elliotxx]

lgtm