Should do what is being done in SonarSource/sonarqube-scan-action, where the major version tag (v5) is updated whenever there is a new minor or patch version within the same major version. I do not want to keep changing my workflows to point to the new minor/patch versions whenever there is a non-breaking change, and I do not want to use master in case there is a breaking change.
Thank you for your work on these actions!
Must-share information (formatted with Markdown):
- which versions are you using (SonarQube Server / Community Build, Scanner, Plugin, and any relevant extension): SonarSource/sonarqube-quality-gate-action v1
- how is SonarQube deployed: N/A
- what are you trying to achieve: use the latest version of the workflow within a major version
- what have you tried so far to achieve this: nothing, the v1 tag needs to be updated whenever a new minor or patch version comes out
Do not share screenshots of logs – share the text itself (bonus points for being well-formatted)!