Automate the Perses version upgrade

[nicolastakashi]

Proposal

Automate Version Update Workflow for Perses Helm Chart

Current Situation

Whenever a new version of Perses is released, we currently need to manually perform the following steps in the perses/helm-charts repository:

1. Update appVersion in chart.yaml.
2. Update version in chart.yaml.
3. Run make update-helm-readme to regenerate the README.

Goal

Automate this process using a GitHub Actions workflow that identifies new releases and automatically updates the required files, then opens a pull request for review.

Proposed Solutions

1. Scheduled Cron Workflow

   • Create a workflow that runs on a regular schedule (e.g., every 6 hours or daily).
   • The workflow would:
     • Check for new releases of Perses.
     • Update the appVersion and version fields in chart.yaml.
     • Run make update-helm-readme.
     • Create a new branch and open a pull request with the changes.

2. Repository Dispatch Event

   • Utilize a repository dispatch event to trigger the workflow when a new release is published in the perses/perses repository.
   • This approach can provide a more immediate response to new releases without waiting for the scheduled cron job.
   • GitHub's repository_dispatch event can be used to trigger the update workflow in perses/helm-charts whenever perses/perses releases a new version.

Benefits

• Reduces manual work and potential human error.
• Ensures timely updates to the Helm chart.
• Streamlines the process of keeping the perses/helm-charts repository aligned with new releases of Perses.