v11 tag does not include the latest version of v11 range

[ego93]

Like most actions in GitHub, which have a major-level tag in this case (v11), should include all subversions under the v11 tag, including the latest version within the v11 range.

Unfortunately for this action it is not the case, can this please be fixed?

[rdhar]

Hey @ego93, that's a great shout. You should now be able to access v11 tag with all the latest minor and patch releases.

The new workflow should automate this process for us going forward for any subsequent major release tags as well.

With that being said, I should call out the security best practice of pinning to a specific SHA to harden your CI/CD pipeline against supply chain attacks.