When using release-commit-sha, it would be helpful to be able to see what the corresponding release tag is. Changing from one SHA to another isn't immediately human-meaningful, but seeing a tag go from something like 0.3.1 to 1.0.0 is very human-meaningful:
Before:
- - uses: actions/checkout@8f4b7f848...
+ - uses: actions/checkout@8e5e7e5ab...
After:
- - uses: actions/checkout@8f4b7f848... # 0.3.1
+ - uses: actions/checkout@8e5e7e5ab... # 1.0.0
I think the tag names must already be known when using release-commit-sha, they're just not getting included in the changes to the yaml, so hopefully this would be easy to implement?
Thanks for your consideration and for maintaining this useful action!