Closed flavio closed 1 year ago
@viccuad that was a regression introduced with the 3.0.1 release. I wonder if I should now update all the references to be 3.0.2 and tag a v3.0.2 release.
Yes. AFAICS, we need to tag a new release and update the policies to use v3.0.2
. This ensures that the update bots will detect the change.
Sigh, what a doozy. Sorry for the replace mistake. Yes, the reusable workflows and GHA in the repo need to be consuming v3.0.2 themselves, prior to tagging a v3.0.2 since https://github.com/kubewarden/github-actions/pull/61.
Ensure the
use
references are expressed in the proper way.@viccuad that was a regression introduced with the 3.0.1 release. I wonder if I should now update all the references to be 3.0.2 and tag a v3.0.2 release.
I'm confused... :thinking: