Previously, due to the lack of releases, the only option was to use the default branch name for the action refs. Using release versions provides a more stable experience for the ordinary users of these actions and also eases ongoing development work on the actions.
Use of the major version ref will cause the workflow to benefit from ongoing development to the action at each patch or minor release up until such time as a new major release is made, at which time the user will be given the opportunity to evaluate whether any changes to the workflow are required by the breaking change that triggered the major release before manually updating the major ref (e.g., uses: arduino/report-size-deltas@v2).
Previously, due to the lack of releases, the only option was to use the default branch name for the action refs. Using release versions provides a more stable experience for the ordinary users of these actions and also eases ongoing development work on the actions.
Use of the major version ref will cause the workflow to benefit from ongoing development to the action at each patch or minor release up until such time as a new major release is made, at which time the user will be given the opportunity to evaluate whether any changes to the workflow are required by the breaking change that triggered the major release before manually updating the major ref (e.g.,
uses: arduino/report-size-deltas@v2
).