Could a "moving" v1 tag be added to this repo ?

[jrfnl]

With action runners, it is generally considered bad practice to use @master as that will get you (the action user) into trouble when the action releases/is working on a new major version.

However, using a specific tag or even a specific commit @v1.7.1 means you continuously have to update the workflow. This is made easier with Dependabot, but still a pain in the neck.

To work-around this, a lot of action runners have a "moving" tag for each major. For this repo that would currently be v1, this tag would always be at the last tagged release of the 1.x range of releases.

By the time, a new major would be released, a new, moving v2 tag would then be added, which does the same for the 2.x range of releases.

That way, end-users only have to update their workflow on new majors (from @v1 to @v2), which Dependabot can handle, and they can avoid using @master and prevent unexpected surprises.

Would you be willing to consider this ?

[srvaroa]

Sure, this makes total sense!

I've updated the README and added a v1. I'll keep this one up to date with future releases. Let me know if that works well.

[jrfnl]

Thank you @srvaroa !