All our repos are reusing actions with by using @main version. The actions are evolving, which is normal, but that breaks those support branches.
We need to start creating tags or at least branches on knative/actions.
When incompatibility occurs we could switch failing repo to older, passing action ie.: @release-1.7. This approach has a disadvantage. People may be confused why their stable branch is broken...
We could also consider to proactively switch actions to branch of knative/actions at release day. This adds churn, but it ensures we can always release if needed.
All our repos are reusing actions with by using
@mainversion. The actions are evolving, which is normal, but that breaks those support branches.We need to start creating tags or at least branches on knative/actions.
When incompatibility occurs we could switch failing repo to older, passing action ie.:
@release-1.7. This approach has a disadvantage. People may be confused why their stable branch is broken...We could also consider to proactively switch actions to branch of
knative/actionsat release day. This adds churn, but it ensures we can always release if needed.