MON-3289: github action to update downstream version in CMO #1
Conversation
… event which happens when upstream -> downstream PR is merged with openshift repos. Once the event occurs, newly added action invokes rhobs/syncbot workflow which creates PR to bump the version.yaml. Signed-off-by: Jayapriya Pai <[email protected]>
|
Looking at other rhobs repositories, I'm not sure that the workflow is useful? For instance https://github.com/rhobs/prometheus-operator/actions/workflows/update-version.yaml has no run in the recent months. I think that we rely on the periodic https://github.com/rhobs/syncbot/actions/workflows/update-cmo-deps-versions.yaml instead. |
sure, I think we can wait on this then. I will review after downstream is updated once rhobs/syncbot#55 is merged |
Vulnerability #1: GO-2024-2611 Infinite loop in JSON unmarshaling in google.golang.org/protobuf More info: https://pkg.go.dev/vuln/GO-2024-2611 Module: google.golang.org/protobuf Found in: google.golang.org/[email protected] Fixed in: google.golang.org/[email protected] Example traces found: #1: json.Decoder.Peek #2: json.Decoder.Read openshift#3: protojson.Unmarshal openshift#4: protojson.UnmarshalOptions.Unmarshal Signed-off-by: Damien Grisonnet <[email protected]>
This commit adds a github action listener for branch delete event which
happens when upstream -> downstream PR is merged with openshift repos.
Once the event occurs, newly added action invokes rhobs/syncbot workflow
which creates PR to bump the version.yaml.
What this PR does / why we need it:
Which issue(s) this PR fixes (optional, in
fixes #<issue number>(, fixes #<issue_number>, ...)format, will close the issue(s) when PR gets merged):Fixes #