Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Rename GITHUB_REF_NAME #147

Closed
rlespinasse opened this issue Oct 22, 2024 · 1 comment · Fixed by #149
Closed

Rename GITHUB_REF_NAME #147

rlespinasse opened this issue Oct 22, 2024 · 1 comment · Fixed by #149
Assignees
Labels
enhancement New feature or request released on @v5.x

Comments

@rlespinasse
Copy link
Owner

Note

As identified in issue #104, this action currently uses the GITHUB_REF_NAME variable for a flexible feature, which covers various GitHub references such as branches or tags. However, GitHub has recently introduced its own usage of GITHUB_REF_NAME for a similar, but not identical, purpose.

To avoid potential conflicts, we will rename the GITHUB_REF_NAME environment variable in this action. This update will be a breaking change and will be introduced in the upcoming v5 release series.

Here are some proposed new names:

  • CURRENT_REF: A general term that continues to accommodate both branches and tags.
  • GITHUB_REF_POINT: To highlight that it refers to a specific reference point (not a commit) within GitHub.
@rlespinasse
Copy link
Owner Author

rlespinasse commented Nov 5, 2024

🎉 This issue has been resolved in version 5.0.0 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request released on @v5.x
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant