damccorm commented on code in PR #38711: URL: https://github.com/apache/beam/pull/38711#discussion_r3544386062
########## .github/workflows/beam_Upgrade_GCP_BOM.yml: ########## @@ -0,0 +1,85 @@ +# Licensed to the Apache Software Foundation (ASF) under one or more +# contributor license agreements. See the NOTICE file distributed with +# this work for additional information regarding copyright ownership. +# The ASF licenses this file to You under the Apache License, Version 2.0 +# (the "License"); you may not use this file except in compliance with +# the License. You may obtain a copy of the License at +# +# http://www.apache.org/licenses/LICENSE-2.0 +# +# Unless required by applicable law or agreed to in writing, software +# distributed under the License is distributed on an "AS IS" BASIS, +# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. +# See the License for the specific language governing permissions and +# limitations under the License. + +name: Upgrade GCP Libraries BOM + +on: + schedule: + - cron: "0 0 * * 0" # Weekly on Sundays at 00:00 UTC Review Comment: > So the main drivers for this workflow are consistently having a weekly upgrade to minimize vulnerabilities, having a process in place so that we don't forget to do the upgrade, and having a workflow if we wanted to at any given point in time just run it and have a new PR ready to go without having to do anything locally. Thanks - for context, BOM upgrades close to the cut have caused bugs to slip through in the past, so the risk here is real. On the other hand, I have not seen problematic CVEs that represent real vulnerabilities slip through (just noise) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
