Expand the bump component action
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 608
- Forks
- 263
- Avg merge
- 1d 3h
- Merged PRs (30d)
- 125
Description
There are three things, we need to do to bump a component
- Change the version in go.mod file if you are using that component as dep.
It is automated by dependabot GitHub action.
- Change the component version in components.yaml file.
We have a self-written binary for that and it checks if there is any new release, if new release it raises a PR to change the version. The job is written as a GitHub action.
- Update the version in CSV
This part is still not automated and we need to raise manual PRs for this. We need to automate this either in our binary or through some other methods.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing the existing self-written binary and GitHub Action that checks component releases and updates components.yaml; compare this with the Dependabot workflow for go.mod. Determine how the component version is represented in the CSV, then automate its update through the existing binary or workflow. Done means a component release updates the CSV without a manual PR.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, go
- Domain
- ci-cd, tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100