Is your feature request related to a problem? Please describe.
It is not really related to a problem. Just a personal wish and reduction of maintenance in my pipeline.
Describe the solution you'd like
I noticed that using nefrob/pr-description@v1 currently fails in GitHub Actions because the v1 tag does not exist. Users are forced to use the specific version v1.2.0.
To follow GitHub Actions' best practices, could you please create and maintain a major version tag v1?
Why is this helpful?
- It allows users to reference
@v1 and automatically receive non-breaking updates and bug fixes (like v1.2.0) without manual intervention.
- It is the standard way most GitHub Actions are consumed (e.g., actions/checkout@v4).
How to implement
- Point a v1 git tag to the same commit as your latest minor release.
Is your feature request related to a problem? Please describe.
It is not really related to a problem. Just a personal wish and reduction of maintenance in my pipeline.
Describe the solution you'd like
I noticed that using nefrob/pr-description@v1 currently fails in GitHub Actions because the v1 tag does not exist. Users are forced to use the specific version v1.2.0.
To follow GitHub Actions' best practices, could you please create and maintain a major version tag v1?
Why is this helpful?
@v1and automatically receive non-breaking updates and bug fixes (like v1.2.0) without manual intervention.How to implement