On the Hacktoberfest. Help us to get an understanding on where we are as a project. We can use this to get some SHIPs implemented. As a goal, we can aim for a 25% of the issues that are label with /hacktoberfest . Next steps, define issues and label them.
From https://github.com/shipwright-io/build/issues/1346, we considered to open it publicly due to its low severity. The community will work on hardening our setup, based on the exploit in Tekton, but we consider that this is not putting us at risk. Furthermore, we think it might be a good opportunity to explore how can SHP generate CVE's for its own packages. On CVE handling, we should consider to assess impact first(prior to CVE issue creation). @adambkaplan to follow-up on this with RH Security Team.
On v0.12.0 release, we did a weekly check on this, things are moving forward(webhook wise).
From @SaschaSchwarze0 , we are moving repos to go v1.20.* , probably a good idea for folks to do this locally.